Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.peureka/agentlookup-mcp

NPM · AGENTLOOKUP-MCP · SCANNED AUG 3

Search, discover, and register AI agents in the public registry at agentlookup.dev.

Available components

+23 this week 69 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • 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 Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · agentlookup-mcp

# add to Claude Code
claude mcp add peureka-agentlookup-mcp -- npx -y agentlookup-mcp
# add to Codex CLI
codex mcp add peureka-agentlookup-mcp -- npx -y agentlookup-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "peureka-agentlookup-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "agentlookup-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add peureka-agentlookup-mcp --command npx --arg -y --arg agentlookup-mcp
# ~/.hermes/config.yaml
mcp_servers:
  peureka-agentlookup-mcp:
    command: "npx"
    args: ["-y", "agentlookup-mcp"]
// mcp.json
{
  "mcpServers": {
    "peureka-agentlookup-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agentlookup-mcp"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +3
    • Stability: unverified → 0.23 functional
  • 2 Aug 26 +23
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass 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
    • Maintenance: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • License: pass → unverified functional
    • Capabilities: pass → unverified functional
    • Dependency health: unverified → partial functional
    • Licence: MIT functional
  • 31 Jul 26 +28
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −65
    • Known CVEs: partial → unverified security
    • Malware scan: pass → unverified security
    • Dependency health: partial → unverified functional
    • Tool coverage: 100 → unverified functional
  • 29 Jul 26 +55
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Maintenance: unverified → pass functional
    • License: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • Schema quality: unverified → excellent functional
    • Licence: MIT functional
  • 28 Jul 26 −21
    • Tool coverage: 100 → unverified functional
    • Dependency health: unverified → partial functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 46

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~499 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
categorystringFilter 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.

NameTypeReqDescription
heartbeat_tokenstringyesThe 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.

NameTypeReqDescription
agent_idstringyesThe 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.

NameTypeReqDescription
capabilitiesarrayWhat the agent can do (e.g. ["scheduling", "calendar-read"])
descriptionstringOne-line description of what the agent does
endpointstringyesThe agent's URL — where other agents can reach it
namestringyesHuman-readable agent name
protocolsarrayCommunication protocols (e.g. ["mcp", "rest"])
webhook_urlstringHTTPS 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.

NameTypeReqDescription
capabilitystringExact capability match (e.g. code-review, translation, scheduling)
protocolstringExact protocol match (e.g. mcp, http-rest, graphql)
querystringFreetext search against name, description, capabilities

No output schema declared.

No examples provided.