agent-config
NPM · @EVENT4U/AGENT-CONFIG
Governed skills, rules and commands for AI coding agents, served by a read-only MCP server.
Available components
Last scanned (3 hours ago)
Scores higher than 81% of npm servers
Category Developer Tools
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 Security99
- 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
- 55 of 197 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to event4u-app/agent-config). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- 84% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 5308 tokens (~21/item across 244 items; 2 tools + 242 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +11
- CVE-2026-118773 no longer affects this package ▲ security
- CVE-2026-118764 no longer affects this package ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.88 ▲ functional
- 4 Nov 26 −8
- Tool safety: pass → unverified ▼ security
- Known CVEs: fail → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: 0.88 → unverified ▼ functional
- Schema quality: 84 → unverified ▼ functional
- First check of Tool coverage: 100 functional
- Package version: 19.2.0 → 20.1.0 functional
- Package version: 19.2.0 → 20.0.0 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 84 → unverified ▼ functional
- Package version: 19.1.0 → 19.2.0 functional
- 31 Oct 26 +14
- CVE-2026-118764 affects this package: medium ▼ security
- CVE-2026-118773 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 19.0.0 → 19.1.0 functional
- 28 Oct 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 84 → unverified ▼ functional
- Package version: 18.2.0 → 19.0.0 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/@event4u/agent-config@20.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | event4u-app/agent-config |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/event4u-app/agent-config/.github/workflows/publish-npm.yml@refs/tags/20.1.0 |
| Rekor log index | 3687605481 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5157190625202ed17b45b74e4c4d418ac81427db77c8b6b8344614fccb6b527286a3f2556bbc9f8b9737a62800c19cedaca28fa0e0d751d2f378cee40 |
Background: How many MCP packages publish verified provenance →
Dependencies 197 packages
| Packages resolved | 197 |
|---|---|
| Stale | 54 |
| No linked repository | 1 |
| 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 →
read_skill ~32
Return one skill body by name, as listed by suggest_skill_for_task.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Skill name. |
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| description | string | – | – |
| error | string | – | – |
| name | string | – | – |
| source | string | – | – |
| status | string | yes | – |
No examples provided.
suggest_skill_for_task ~127
Rank skills against a free-form task description. Use when the skill you need is not in the catalogue the host delivered, so asking by name is impossible and asking by task is not. Each row carries the skill's own description — its routing criteria, including any clause saying when to use something else. CHOOSE BY READING THE ROWS, then open at most two bodies with read_skill. Returns names, scores, personas and descriptions — never bodies.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results. Default 8. |
| task | string | yes | The task to match skills against. |
| Name | Type | Req | Description |
|---|---|---|---|
| clamped_from | number | – | – |
| error | string | – | – |
| skills_indexed | number | – | – |
| status | string | yes | – |
| suggestions | array | yes | – |
| tier_filter | string | – | – |
| tiers | string | – | – |
No examples provided.
How do I install the agent-config MCP server?
agent-config runs locally as an npm package, launched with npx -y @event4u/agent-config. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @event4u/agent-config
claude mcp add event4u-app-agent-config -- npx -y @event4u/agent-config
What is the agent-config MCP server?
agent-config is an MCP server listed in the public MCP registry as io.github.event4u-app/agent-config. Governed skills, rules and commands for AI coding agents, served by a read-only MCP server. This page covers its npm package (@event4u/agent-config).
Is the agent-config MCP server safe to use?
agent-config scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 agent-config MCP server expose?
agent-config exposes 2 tools: suggest_skill_for_task, read_skill. Their descriptions and schemas cost roughly 159 tokens of context every time the server is loaded.
Is the agent-config MCP server still maintained?
agent-config is still listed as active in the MCP registry. We last reached this channel on 5 November 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 agent-config MCP server under?
agent-config declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.