getspctre/spctre (getspctre/spctre) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
7 days ago

getspctre/spctre

MCP server for Spctre policy governance

→ getspctre/spctre· npm: @spctre/mcp-server· listed on npm

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

getspctre

Source: npm

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

npm

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: SPCTRE_API_REFRESH_TOKEN, SPCTRE_API_TOKEN, SPCTRE_MCP_AUDIT_SEAL_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configOTEL_METRIC_EXPORT_INTERVAL
configOTEL_SERVICE_NAME
configSPCTRE_AGENT_IDexport =your-agent-id
configSPCTRE_ALLOWED_CONNECTORS
configSPCTRE_ALLOWED_SOURCE_IPS
configSPCTRE_ALLOWED_TOOLS
🔐 secretSPCTRE_API_REFRESH_TOKENSPCTRE_API_TOKEN or in HTTP mode; the caller's
🔐 secretSPCTRE_API_TOKENexport =your-service-token
configSPCTRE_API_URLexport =http://localhost:3000
configSPCTRE_LOG_STDERR
🔐 secretSPCTRE_MCP_AUDIT_SEAL_SECRET
configSPCTRE_MCP_HTTP_PATHexport =/mcp
configSPCTRE_MCP_HTTP_PORTexport =8090
configSPCTRE_MCP_HTTP_RATE_LIMIT_BURST
configSPCTRE_MCP_HTTP_RATE_LIMIT_PER_SECOND
configSPCTRE_MCP_OAUTH_ISSUERexport =https://app.spctre.dev
configSPCTRE_MCP_OAUTH_RESOURCEexport =https://mcp.example.com/mcp
configSPCTRE_MCP_OAUTH_SCOPESexport =mcp:read,mcp:write
configSPCTRE_MCP_REQUIRE_BEARER_AUTH
configSPCTRE_WORKSPACE_IDexport =ws-your-workspace
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

10/10 tools missing one or more hints — evaluate_policy (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_evidence_record (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); escalate_to_review (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/spctre-mcp-server-1laqmo)](https://m8ven.ai/mcp/spctre-mcp-server-1laqmo)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 140d32555cb00f916ed3799405eed977c8402685
code hash: 7682ef789db915cb63ae2e227b9a61de24df421c5d0fd0f8a3f6cc5915ec7331
verified: 8/19/2026, 9:36:18 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client