io.github.Gareth1953/agent-services-mcp
NPM · AGENT-SERVICES-MCP · SCANNED SEP 20
MCP server: x402-paid & free tools for AI agents — provenance, quality scoring, action audit.
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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 90 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1595 tokens (~227/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 (57% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 io.github.Gareth1953/agent-services-mcp server?
io.github.Gareth1953/agent-services-mcp runs locally as an npm package, launched with npx -y agent-services-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agent-services-mcp
claude mcp add gareth1953-agent-services-mcp -- npx -y agent-services-mcp
{
"mcpServers": {
"gareth1953-agent-services-mcp": {
"command": "npx",
"args": [
"-y",
"agent-services-mcp"
]
}
}
} {
"servers": {
"gareth1953-agent-services-mcp": {
"command": "npx",
"args": [
"-y",
"agent-services-mcp"
]
}
}
} codex mcp add gareth1953-agent-services-mcp -- npx -y agent-services-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gareth1953-agent-services-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"agent-services-mcp"
],
"enabled": true
}
}
} openclaw mcp add gareth1953-agent-services-mcp --command npx --arg -y --arg agent-services-mcp
mcp_servers:
gareth1953-agent-services-mcp:
command: "npx"
args: ["-y", "agent-services-mcp"] {
"McpServers": {
"gareth1953-agent-services-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"agent-services-mcp"
]
}
}
} assistant mcp add gareth1953-agent-services-mcp -t stdio -c npx -a -y agent-services-mcp
{
"mcpServers": {
"gareth1953-agent-services-mcp": {
"command": "npx",
"args": [
"-y",
"agent-services-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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/agent-services-mcp@0.2.1
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 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
audit_action Audit an agent action ~406
PAID (x402 micropayment in USDC on Base; exact amount is returned in the 402 challenge — pay via x_payment). Creates a tamper-evident AUDIT RECEIPT for an action an agent took: an Ed25519-signed receipt over a SHA-256 hash of the action, your caller-attested actor_metadata, a hash of optional context, and a timestamp. USE WHEN you need an accountability record proving exactly what an agent claimed it did, and when. Verify later for FREE with verify_audit. PROVES: the action RECORD is genuine (issued by the service's signing key) and unaltered since issue. DOES NOT PROVE: that the agent's claim is true. action/actor_metadata/context are CALLER-ATTESTED — proof you CLAIMED this exact record, not that the agent did it, nor that it was authorized or correct. An accountability/audit tool, NOT a lie-detector. Two-step: call once with no x_payment to get the 402 requirements, then resend with x_payment to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What the agent did (the action being audited). Non-empty. |
| actor_metadata | object | yes | Caller-attested: who/what performed the action and the stated authority it acted under (e.g. { agent, operator, authority }). Recorded verbatim and covered by the signature; proves you claimed it, no… |
| context | object | – | Optional caller-attested supporting detail. Hashed into the receipt; an absent context hashes the canonical empty object. |
| x_payment | string | – | Optional x402 payment token (the base64 X-PAYMENT value). Leave unset on the first call to receive the 402 payment requirements; then build the token with an x402 client + wallet and resend it here t… |
No output schema declared.
No examples provided.
certify_provenance Certify content provenance ~340
PAID (x402 micropayment in USDC on Base; exact amount is returned in the 402 challenge — pay via x_payment). Certifies the ORIGIN of content: returns an Ed25519-signed receipt over a SHA-256 hash of the content, your caller-attested generator_metadata, and a service timestamp. USE WHEN you need tamper-evident proof of exactly what content existed at a point in time. Verify it later for FREE with verify_provenance. PROVES: the content is unmodified (hash) and the receipt was issued by the holder of the service's signing key. DOES NOT PROVE: generator_metadata — the receipt proves you CLAIMED that metadata, not that a specific model produced the content. Proof-of-origin/tamper-evidence, NOT AI-detection and NOT a truth guarantee. Two-step: call once with no x_payment to get the 402 requirements, then resend with x_payment to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The exact content to certify. Non-empty. |
| generator_metadata | object | – | Optional caller-attested metadata about what generated the content (e.g. { model, provider }). Recorded verbatim; the receipt proves you claimed it, not that a specific model ran. |
| x_payment | string | – | Optional x402 payment token (the base64 X-PAYMENT value). Leave unset on the first call to receive the 402 payment requirements; then build the token with an x402 client + wallet and resend it here t… |
No output schema declared.
No examples provided.
get_quality_rubric Get the published quality rubric ~56
FREE; takes no input. Fetch the published Quality Gate rubric (markdown) + its version that score_quality grades against. USE WHEN you want to understand exactly what a quality score means and does not mean before calling score_quality.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
score_quality Score content against the published quality rubric ~355
PAID (x402 micropayment in USDC on Base; exact amount is returned in the 402 challenge — pay via x_payment). Scores content against quality-gate's PUBLISHED rubric (clarity, completeness, internal consistency, obvious-error freedom — 0–25 each, summing 0–100) and returns an Ed25519-signed score receipt. Read the exact rubric for FREE with get_quality_rubric. USE WHEN you need a reproducible, signed quality score for a piece of content. RETURNS: a signed score receipt; or, with target_score set, receipt:null + the failing breakdown ('no pass, no pay' — no receipt and no charge below target). WHAT IT IS NOT: a measure of absolute truth, an external/third-party standard, or a fact-check. Two-step: call once with no x_payment to get the 402 requirements, then resend with x_payment to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content to score. Non-empty. |
| rubric_version | string | – | Optional rubric version to score against; must match the service's current version (e.g. "v1") if provided. |
| target_score | number | – | Optional 0–100 threshold. Enables 'no pass, no pay': below this, no receipt is issued and no charge is made. |
| x_payment | string | – | Optional x402 payment token (the base64 X-PAYMENT value). Leave unset on the first call to receive the 402 payment requirements; then build the token with an x402 client + wallet and resend it here t… |
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | object | – | Per-dimension scores and flags. |
| receipt | – | – | Signed score receipt, or null if below target_score (no pass, no pay). |
| score | number | – | Total score 0–100, when present. |
No examples provided.
verify_audit Verify an audit receipt ~184
FREE. Verifies an audit receipt against its record (re-hashes the submitted action + context, checks they and actor_metadata match the receipt, plus the Ed25519 signature). USE WHEN you have an audit receipt + the original action/metadata and need to confirm the record is genuine and unaltered. RETURNS: { valid, details }. valid is true only if action, context, AND actor_metadata all match the receipt AND the signature is valid. A 200 means verification ran — always read valid (false = record altered or receipt forged).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The action the receipt was issued for. |
| actor_metadata | object | yes | The actor_metadata the receipt was issued for. |
| context | object | – | The optional context the receipt was issued for (omit if none). |
| receipt | object | yes | An audit receipt as returned by audit_action. |
| Name | Type | Req | Description |
|---|---|---|---|
| details | object | – | Per-check breakdown (e.g. hash match, signature valid). |
| valid | boolean | yes | True only if the content/record matches the receipt AND the Ed25519 signature is valid. |
No examples provided.
verify_provenance Verify a provenance receipt ~138
FREE. Verifies a provenance receipt against its content (re-hashes the content, checks the Ed25519 signature). USE WHEN you have a receipt + the original content and need to confirm it's genuine and unmodified. RETURNS: { valid, details }. valid is true only if the content hash matches the receipt AND the signature is valid under the service's public key. A 200 means verification ran — always read valid (false = content modified or receipt altered/forged).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content to check against the receipt. |
| receipt | object | yes | A provenance receipt as returned by certify_provenance. |
| Name | Type | Req | Description |
|---|---|---|---|
| details | object | – | Per-check breakdown (e.g. hash match, signature valid). |
| valid | boolean | yes | True only if the content/record matches the receipt AND the Ed25519 signature is valid. |
No examples provided.
verify_quality Verify a quality score receipt ~116
FREE. Verifies a quality score receipt against its content (re-hashes the content, checks the Ed25519 signature, which covers the score itself — so a forged or altered score fails). USE WHEN you have a score receipt + the content and need to confirm the score is genuine. RETURNS: { valid, details }. A 200 means verification ran — always read valid.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content the score receipt was issued for. |
| receipt | object | yes | A quality score receipt as returned by score_quality. |
| Name | Type | Req | Description |
|---|---|---|---|
| details | object | – | Per-check breakdown (e.g. hash match, signature valid). |
| valid | boolean | yes | True only if the content/record matches the receipt AND the Ed25519 signature is valid. |
No examples provided.
What is the io.github.Gareth1953/agent-services-mcp server?
io.github.Gareth1953/agent-services-mcp is listed in the public MCP registry as io.github.Gareth1953/agent-services-mcp. MCP server: x402-paid & free tools for AI agents, provenance, quality scoring, action audit. This page covers its npm package (agent-services-mcp).
Is the io.github.Gareth1953/agent-services-mcp server safe to use?
io.github.Gareth1953/agent-services-mcp scores 82 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 io.github.Gareth1953/agent-services-mcp server expose?
io.github.Gareth1953/agent-services-mcp exposes 7 tools: certify_provenance, verify_provenance, score_quality, verify_quality, get_quality_rubric, and 2 more. Their descriptions and schemas cost roughly 1,595 tokens of context every time the server is loaded.
Is the io.github.Gareth1953/agent-services-mcp server still maintained?
io.github.Gareth1953/agent-services-mcp 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 io.github.Gareth1953/agent-services-mcp server under?
io.github.Gareth1953/agent-services-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.