io.github.peureka/agentlookup-mcp
NPM · AGENTLOOKUP-MCP · SCANNED SEP 22
Search, discover, and register AI agents in the public registry at agentlookup.dev.
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 205 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 499 tokens (~83/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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; "heartbeat" implies "send" 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 6 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.peureka/agentlookup-mcp server?
io.github.peureka/agentlookup-mcp runs locally as an npm package, launched with npx -y agentlookup-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 · agentlookup-mcp
claude mcp add peureka-agentlookup-mcp -- npx -y agentlookup-mcp
{
"mcpServers": {
"peureka-agentlookup-mcp": {
"command": "npx",
"args": [
"-y",
"agentlookup-mcp"
]
}
}
} {
"servers": {
"peureka-agentlookup-mcp": {
"command": "npx",
"args": [
"-y",
"agentlookup-mcp"
]
}
}
} codex mcp add peureka-agentlookup-mcp -- npx -y agentlookup-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"peureka-agentlookup-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"agentlookup-mcp"
],
"enabled": true
}
}
} openclaw mcp add peureka-agentlookup-mcp --command npx --arg -y --arg agentlookup-mcp
mcp_servers:
peureka-agentlookup-mcp:
command: "npx"
args: ["-y", "agentlookup-mcp"] {
"McpServers": {
"peureka-agentlookup-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"agentlookup-mcp"
]
}
}
} assistant mcp add peureka-agentlookup-mcp -t stdio -c npx -a -y agentlookup-mcp
{
"mcpServers": {
"peureka-agentlookup-mcp": {
"command": "npx",
"args": [
"-y",
"agentlookup-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.
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 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.
- 18 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 −2
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 22 Sept 2026 · Analysed npm/agentlookup-mcp@1.0.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 →
discover_agents ~62
Browse new, active, and popular agents in the registry. Use when exploring what's available, starting a new project and looking for useful integrations, or when no specific search terms exist.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category. Default: mixed results from all three. |
No output schema declared.
No examples provided.
heartbeat ~57
Send a heartbeat to keep a registered agent's status active. Use when managing an agent that's already registered and needs to stay active. Requires the agent's heartbeat token.
| Name | Type | Req | Description |
|---|---|---|---|
| heartbeat_token | string | yes | The agent's heartbeat token (hb_live_*) |
No output schema declared.
No examples provided.
lookup_agent ~72
Get full details for a specific agent by ID. Use when an agent_id is known from search results, from a .well-known/agents.json file, or from a user providing one.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent's ID (e.g. ag_acme-scheduler_x7k2m) |
No output schema declared.
No examples provided.
register_agent ~156
Register a new agent in the public registry. Use when the user wants to make their agent discoverable, or when an autonomous agent decides to register itself. The secret and tokens are returned once and never again — present them to the user clearly.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | What the agent can do (e.g. ["scheduling", "calendar-read"]) |
| description | string | – | One-line description of what the agent does |
| endpoint | string | yes | The agent's URL — where other agents can reach it |
| name | string | yes | Human-readable agent name |
| protocols | array | – | Communication protocols (e.g. ["mcp", "rest"]) |
| webhook_url | string | – | HTTPS URL for receiving notifications |
No output schema declared.
No examples provided.
registry_status ~41
Check the health and stats of the AgentLookup registry. Use when the user asks about the registry's status, or to verify the registry is operational before other calls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_agents ~111
Find agents by capability, protocol, or freetext query. Use when the user asks to find an agent, when a task requires a capability the current agent doesn't have, or when exploring what agents exist for a domain.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Exact capability match (e.g. code-review, translation, scheduling) |
| protocol | string | – | Exact protocol match (e.g. mcp, http-rest, graphql) |
| query | string | – | Freetext search against name, description, capabilities |
No output schema declared.
No examples provided.
What is the io.github.peureka/agentlookup-mcp server?
io.github.peureka/agentlookup-mcp is listed in the public MCP registry as io.github.peureka/agentlookup-mcp. Search, discover, and register AI agents in the public registry at agentlookup.dev. This page covers its npm package (agentlookup-mcp).
Is the io.github.peureka/agentlookup-mcp server safe to use?
io.github.peureka/agentlookup-mcp 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. 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.peureka/agentlookup-mcp server expose?
io.github.peureka/agentlookup-mcp exposes 6 tools: search_agents, discover_agents, lookup_agent, register_agent, registry_status, heartbeat. Their descriptions and schemas cost roughly 499 tokens of context every time the server is loaded.
Is the io.github.peureka/agentlookup-mcp server still maintained?
io.github.peureka/agentlookup-mcp 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 io.github.peureka/agentlookup-mcp server under?
io.github.peureka/agentlookup-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.