MCP spec 2026-07-28 goes final: 10,000+ servers must migrate. Time left: …Check your server now →
ScannerRegistryThe BatteryVerified BadgeControlPricingFor vendorsFor enterprisesFAQScan a server free →
Agent Tool Risk Report

mcp.context7.com

Generated by the Conformant public-subset battery and anchored to the Sigstore/Rekor transparency log. The grade below is tamper-evident: recompute the report’s canonical hash and compare it with the Rekor entry.

https://mcp.context7.com/mcp
Context7 · public-subset battery v2.0.0 · Fri, 14 Aug 2026 07:38:12 GMT · report bcfd3199187babb5
A
Overall A (92/100). Cleared for connection review: no material findings on the public battery.
Second axis · not part of the grade

Spec 2026-07-28 readiness

NOT OBSERVABLE

Not determinable from the public probe. Credential-gated endpoints do not complete an unauthenticated handshake, so the negotiated revision cannot be read. This is a coverage limit, not a finding.

3 of 6 signals evaluable on the public probe · deprecation windows close 2027-07-28
  • RDY-01Transport generationcurrent
    Streamable HTTP: the transport the 2026-07-28 stateless core is built on.
  • RDY-02Protocol revisionn/a
    Revision negotiation could not be observed.
  • RDY-03Stateless corecurrent
    Operates without a session header, matching the 2026-07-28 stateless core.
  • RDY-04Client registrationpartial
    Exposes a Dynamic Client Registration endpoint and does not advertise CIMD support. DCR is deprecated with a window closing 2027-07-28, but CIMD advertisement is not yet consistently published, so this is reported as a migration item rather than a removal finding.
  • RDY-05Cacheable tool catalogn/a
    Tool catalog cache posture not observable.
  • RDY-06Deprecated capabilitiesn/a
    Capability set not observable.

Readiness measures migration posture against the specification finalized 2026-07-28. It is reported separately because a well-authenticated server on deprecated transport is a migration risk, not a security defect — scoring both on one axis would misprice both. Signals that could not be evaluated are excluded from the score rather than counted as passing.

CFM-01AuthenticationWARN
Anonymous by design: every exposed tool is read-only.
  • Open endpoint, read-only surface. The server completes initialize and lists tools without credentials, but all exposed tools are read-only. Acceptable for public-data servers; confirm no tenant-scoped data is reachable.
CFM-02Authorization (OAuth)N/A
No authentication layer present to evaluate (see CFM-01).
CFM-03Tool poisoningPASS
1 suspicious pattern(s) detected across the tool surface.
  • Oversized description. tool "resolve-library-id" is 2006 characters; large descriptions are a common carrier for embedded instructions.
CFM-04Scopes & least privilegePASS
Tool surface (2 tool(s)) is scoped: no over-privilege signals.
CFM-05Secrets exposurePASS
No credential patterns in disclosed tool definitions or instructions.
CFM-06Destructive-tool guardrailsPASS
No destructive-class tools exposed.
CFM-08Transport securityPASS
TLS transport.
CFM-10Exposed configuration surfacePASS
No configuration or credential documents served at well-known paths.
CFM-09Command-injection exposure (advisory)INFO
No command-execution sinks or transport-steering content observed on the public surface. Local STDIO config-injection (OX Security, 2026-04-15) is attested, not remotely testable.
✔ anchoredsha256:bcfd3199187b…72749e→ Sigstore/Rekor logIndex 2463220852verify ↗tamper-evident · independently checkable

Embed this grade

The badge URL is stable per server: weekly re-verification updates the grade and date in place. It links to this live anchored report.

Conformant badge for https://mcp.context7.com/mcp
<a href="https://conformant.io/report/bcfd3199187babb5" target="_blank" rel="noopener">
  <img src="https://conformant.io/api/badge?server=https%3A%2F%2Fmcp.context7.com%2Fmcp" alt="Conformant security grade" width="232" height="44" />
</a>
Scan another serverView the registryGet Cleared-to-Connect →