agentgate
NPM · @ZHILIANGTECH/AGENTGATE · SCANNED SEP 22
Read-only evidence for the tools agents run: MCP server records, coverage and policy.
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ciceroyang/agentgate). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 498 tokens (~124/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 4 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the agentgate MCP server?
agentgate runs locally as an npm package, launched with npx -y @zhiliangtech/agentgate. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @zhiliangtech/agentgate
claude mcp add ciceroyang-agentgate -- npx -y @zhiliangtech/agentgate
{
"mcpServers": {
"ciceroyang-agentgate": {
"command": "npx",
"args": [
"-y",
"@zhiliangtech/agentgate"
]
}
}
} {
"servers": {
"ciceroyang-agentgate": {
"command": "npx",
"args": [
"-y",
"@zhiliangtech/agentgate"
]
}
}
} codex mcp add ciceroyang-agentgate -- npx -y @zhiliangtech/agentgate
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ciceroyang-agentgate": {
"type": "local",
"command": [
"npx",
"-y",
"@zhiliangtech/agentgate"
],
"enabled": true
}
}
} openclaw mcp add ciceroyang-agentgate --command npx --arg -y --arg @zhiliangtech/agentgate
mcp_servers:
ciceroyang-agentgate:
command: "npx"
args: ["-y", "@zhiliangtech/agentgate"] {
"McpServers": {
"ciceroyang-agentgate": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@zhiliangtech/agentgate"
]
}
}
} assistant mcp add ciceroyang-agentgate -t stdio -c npx -a -y @zhiliangtech/agentgate
{
"mcpServers": {
"ciceroyang-agentgate": {
"command": "npx",
"args": [
"-y",
"@zhiliangtech/agentgate"
]
}
}
} 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.
- 21 Sept 26 +3
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Schema quality: 88 → 124 ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: unverified functional
- Package version: 0.3.0 → 0.5.0 functional
- 20 Sept 26 0
- Security disclosure: fail → pass ▲ functional
- 19 Sept 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 18 Sept 26 69
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 22 Sept 2026 · Analysed npm/@zhiliangtech/agentgate@0.5.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 | ciceroyang/agentgate |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ciceroyang/agentgate/.github/workflows/publish.yml@refs/tags/v0.5.0 |
| Rekor log index | 2906324671 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:69a7b979a76a419cbfa4f73b4e4ca070264c6e8a946e6a999ed098b6ba06f63fd522fab2d065d6ce22b2ffffa5e43e0fe3a9c4f21f8d613e89d2c504d |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_project Scan a local project for refused configuration ~155
Run agentgate's own checks over a local directory: MCP client configuration, hooks, manifests and source patterns a policy would refuse. Use it on a project you can read; it is not a record lookup, so for one server's record use lookup_server and for a list of tools use inventory_tools. It only reads files; it does not install, execute or upload anything, and it does not scan the network.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | string | – | Comma-separated directories to skip. Defaults to node_modules,.git |
| policy | string | – | Path to an agentgate.policy.json. Defaults to the one in root, or the built-in default. |
| root | string | – | Directory to check. Defaults to the working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | object | – | what the policy could not measure: a check that failed, and evidence the index did not have |
| findings | array | – | – |
| indexWarning | string | – | Present only when the server was started with a note about the index it loaded. |
| policyVersion | string | – | – |
| relatedRecords | integer | – | – |
| root | string | yes | – |
| verdict | string | yes | clean, findings or incomplete; incomplete is not a pass |
No examples provided.
coverage_report How much of the index was actually measured ~89
Report the coverage distribution of the whole index: how many records are fully measured, what stopped the rest, and how many findings came out of the work that ran. Use this before quoting any percentage from this server, because it is the denominator; it is the same number the project quotes in public. It answers a question about the index, not about one tool: for one tool, use lookup_server.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| completedRuns | integer | – | – |
| cross | object | – | – |
| findings | object | – | – |
| findingsTotal | integer | – | – |
| generatedAt | string|null | – | – |
| indexWarning | string | – | Present only when the server was started with a note about the index it loaded. |
| perScanner | object | – | – |
| problems | array | – | – |
| reasons | object | – | – |
| requiredRuns | integer | – | – |
| scanner | string|null | – | – |
| states | object | – | – |
| total | integer | – | – |
| verdictIncompleteButComplete | integer | – | – |
| verdicts | object | – | – |
No examples provided.
inventory_tools Match a list of tools against the index ~105
Given the MCP servers and agent tools you actually use, report which ones the index has evidence for, which need your exact version, and which it has never measured. Use this to audit a list of what you run; for a single server or package, lookup_server returns the whole record rather than a one-line state. Nothing is uploaded and nothing is executed.
| Name | Type | Req | Description |
|---|---|---|---|
| tools | array | yes | One entry per tool: a name, or an object with name/server/package/registry/version. |
| Name | Type | Req | Description |
|---|---|---|---|
| indexWarning | string | – | Present only when the server was started with a note about the index it loaded. |
| items | array | yes | – |
| summary | object | yes | – |
No examples provided.
lookup_server Look up an MCP server's evidence ~149
Look up one MCP server, or one package, in the local agentgate evidence index. Use this when you know what you are asking about and want its record: the verdict, the coverage block (which scanners ran, which did not, and why), and the findings. Do not use it to check a list of tools you use; inventory_tools answers that question and returns one line per tool instead. A record that is incomplete is reported as incomplete, never as clean.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | – | Package name, for example @scope/pkg |
| server | string | – | Registry server name, for example org.example/tools |
| version | string | – | Exact version, to narrow a package match |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | false means this index has no such record; it is not a statement that the tool is safe or that it does not exist |
| indexGeneratedAt | string|null | – | – |
| indexWarning | string | – | Present only when the server was started with a note about the index it loaded. |
| multiple | boolean | – | present when found is true |
| query | object | – | present when found is false, echoing what was asked |
| record | object | – | One index record, reduced to what a reader can act on. |
| records | array | – | present instead of record when several matched; at most ten are listed |
No examples provided.
What is the agentgate MCP server?
agentgate is an MCP server listed in the public MCP registry as io.github.ciceroyang/agentgate. Read-only evidence for the tools agents run: MCP server records, coverage and policy. This page covers its npm package (@zhiliangtech/agentgate).
Is the agentgate MCP server safe to use?
agentgate scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 agentgate MCP server expose?
agentgate exposes 4 tools: lookup_server, inventory_tools, coverage_report, check_project. Their descriptions and schemas cost roughly 498 tokens of context every time the server is loaded.
Is the agentgate MCP server still maintained?
agentgate is still listed as active in the MCP registry. We last reached this channel on 22 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 agentgate MCP server under?
agentgate declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.