mcp-context-card
NPM · MCP-CONTEXT-CARD · SCANNED SEP 20
MCP server for a project's context (AGENTS.md), memory, and identity — base or drop-in extension.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 661 tokens (~66/item across 10 items; 9 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "forget" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the mcp-context-card server?
mcp-context-card runs locally as an npm package, launched with npx -y mcp-context-card. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-context-card
claude mcp add wolfe-jam-mcp-context-card -- npx -y mcp-context-card
{
"mcpServers": {
"wolfe-jam-mcp-context-card": {
"command": "npx",
"args": [
"-y",
"mcp-context-card"
]
}
}
} {
"servers": {
"wolfe-jam-mcp-context-card": {
"command": "npx",
"args": [
"-y",
"mcp-context-card"
]
}
}
} codex mcp add wolfe-jam-mcp-context-card -- npx -y mcp-context-card
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wolfe-jam-mcp-context-card": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-context-card"
],
"enabled": true
}
}
} openclaw mcp add wolfe-jam-mcp-context-card --command npx --arg -y --arg mcp-context-card
mcp_servers:
wolfe-jam-mcp-context-card:
command: "npx"
args: ["-y", "mcp-context-card"] {
"McpServers": {
"wolfe-jam-mcp-context-card": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-context-card"
]
}
}
} assistant mcp add wolfe-jam-mcp-context-card -t stdio -c npx -a -y mcp-context-card
{
"mcpServers": {
"wolfe-jam-mcp-context-card": {
"command": "npx",
"args": [
"-y",
"mcp-context-card"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 8 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.10 ▲ functional
- Package version: 1.0.0 → 1.1.0 functional
- Package version: 1.0.0 → 1.0.1 functional
- 5 Sept 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/mcp-context-card@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
author_agents_md ~83
Author an AGENTS.md for this project and return the draft — BETTER from repo facts alone (via agents-md-facts: real build/test commands, entry points, toolchain conventions, nothing invented), or BEST when a project.faf exists (facts plus its structured goal/who/why as a second managed block ahead of them). Does not write a file.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
forget ~53
Remove a fact by id — to correct or drop something stale. A missing id is reported, not an error.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The exact id of the fact to remove. Reports whether a fact was actually removed. |
No output schema declared.
No examples provided.
list_agents_md_sections ~36
List the headings in this project's AGENTS.md, so a client can pull one section instead of spending context on the whole file.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_context_sources ~41
What context does this project publish (AGENTS.md, memory, identity), in what media types, and through which discovery surface. For a client connecting cold.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_agents_md ~70
Return this project's AGENTS.md — the whole file, or one section by heading. The instructions a client would otherwise have to know to look for and read wholesale.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | A heading to return just that section (case-insensitive, prefix match). Omit for the whole file. |
No output schema declared.
No examples provided.
recall ~60
Retrieve a fact stored in a previous session by id. Exact lookup — not fuzzy or substring.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The exact id a previous remember call used. Returns the stored text, or a "no memory for <id>" message if nothing matches. |
No output schema declared.
No examples provided.
remember ~149
Persist a fact past the session boundary — written to a .fafm file, not held in memory. Reusing an existing id replaces that fact's text in place (no duplicate); a new id appends. Facts are written verification_status: unverified.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A stable key you choose for this fact — pass the same id later to recall or forget it. Exact match, case-sensitive, any string; keep it short and meaningful (e.g. "deploy-target", "db-url"). Reusing… |
| text | string | yes | The fact itself, as plain prose. Stored verbatim and returned as-is by recall. |
No output schema declared.
No examples provided.
render_context_card ~122
Render the whole card — identity, AGENTS.md, memory, discovery — as one self-contained HTML page a person can read or screenshot. AGENTS.md sections collapse by default; pass expanded:true for the full render. Also served at GET /card (?expand=all) over the HTTP transport.
| Name | Type | Req | Description |
|---|---|---|---|
| accent | string | – | CSS hex colour, e.g. #FF702D (default: the AAIF palette) |
| expanded | boolean | – | render every AGENTS.md section open (default: collapsed) |
| theme | string | – | default: auto |
No output schema declared.
No examples provided.
whoami ~31
This server's own identity — name, vendor, version, status, license — from its .fafa card.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the mcp-context-card server?
mcp-context-card is listed in the public MCP registry as io.github.Wolfe-Jam/mcp-context-card. MCP server for a project's context (AGENTS.md), memory, and identity, base or drop-in extension. This page covers its npm package (mcp-context-card).
Is the mcp-context-card server safe to use?
mcp-context-card scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the mcp-context-card server expose?
mcp-context-card exposes 9 tools: read_agents_md, author_agents_md, list_agents_md_sections, remember, recall, and 4 more. Their descriptions and schemas cost roughly 645 tokens of context every time the server is loaded.
Is the mcp-context-card server still maintained?
mcp-context-card is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the mcp-context-card server under?
mcp-context-card declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.