generated: '2026-09-19'
method: searched
status: published
source: https://www.npmjs.com/package/@mbeato/apimesh-mcp-server
docs: https://github.com/mbeato/APIMesh#install-the-mcp-server
summary: >-
  APIMesh ships two first-party MCP servers, both distributed as npm packages that run locally
  over stdio. @mbeato/apimesh-mcp-server (v1.8.2, 2026-04-26) registers 76 tools that call the
  pay-per-call marketplace APIs on *.apimesh.xyz — 74 analysis tools plus wallet_usage and
  wallet_set_cap — and is listed in the official MCP registry as io.github.mbeato/apimesh, on
  Smithery and on Glama. @mbeato/agentcontext-mcp (v0.1.2, 2026-04-29) is the MCP face of the
  agentsmd wedge with two tools (read_agent_context, convert_agent_context). The provider operates
  no remote MCP endpoint: RETIRED.md names a former self-hosted HTTP server at mcp.apimesh.xyz,
  which now returns {"error":"Not found"}, and the apex /mcp path returns 401.
deployment:
  mode: local-stdio
  endpoint: null
  install: npx @mbeato/apimesh-mcp-server
  package: https://www.npmjs.com/package/@mbeato/apimesh-mcp-server
  auth: none
  verified: searched
  note: >-
    mode is local-stdio: an MCP client launches the npm binary (bin apimesh-mcp) as a child
    process; nothing is reachable by an agent until a human installs it. The MCP registry entry
    declares transport type stdio. auth is none for the MCP handshake itself; the tools call
    HTTP 402 pay-per-call endpoints and need an optional WALLET_PRIVATE_KEY environment variable
    (USDC on Base via x402) for paid calls — free /preview tiers needed nothing. verified is
    searched (npm registry metadata, MCP registry record, and the server.ts source were read;
    the binary was not executed). mcp-server/http.ts in the repo is a Streamable HTTP variant
    bound to 127.0.0.1 only — not a public endpoint. Probed 2026-09-19: https://mcp.apimesh.xyz/
    404, https://apimesh.xyz/mcp 401.
liveness:
  checked: '2026-09-19'
  finding: >-
    The 74 analysis tools call https://<api-name>.apimesh.xyz/... hosts that the provider retired
    on 2026-05-11 (apis/RETIRED.md, commit "retire marketplace APIs, focus on wedges"). Every one
    of the 23 hosts named in the served OpenAPI, and check.apimesh.xyz, now answers 404
    {"error":"Unknown API: <name>"}; only /wallet/{address} on the apex still answers 200. The
    package remains installable and its tools/list remains real, but a tool call today returns
    the upstream 404. The provider has not unpublished or deprecated the package.
servers:
- id: apimesh
  name: APIMesh MCP Server
  package: '@mbeato/apimesh-mcp-server'
  version: 1.8.2
  published: '2026-04-26'
  registry: npm
  registry_url: https://www.npmjs.com/package/@mbeato/apimesh-mcp-server
  mcp_registry: io.github.mbeato/apimesh
  mcp_registry_url: https://registry.modelcontextprotocol.io/v0/servers?search=apimesh
  smithery: https://smithery.ai/servers/apimesh/apimesh-mcp-server
  glama: https://glama.ai/mcp/servers/mbeato/APIMesh
  transport: stdio
  bin: apimesh-mcp
  install: npx @mbeato/apimesh-mcp-server
  client_config:
    mcpServers:
      apimesh:
        command: npx
        args: ['@mbeato/apimesh-mcp-server']
  environment:
  - name: WALLET_PRIVATE_KEY
    required: false
    secret: true
    description: USDC wallet private key for x402 payments (hex). Required for paid endpoints; free /preview endpoints work without it.
  source_code: https://github.com/mbeato/APIMesh/tree/main/mcp-server
  license: MIT
  tool_count: 76
  tools_file: mcp/apimesh-xyz-mcp-tools.json
  tools_source: >-
    Names, descriptions and zod input schemas parsed 2026-09-19 from mcp-server/server.ts at
    github.com/mbeato/APIMesh@main (the same file the published 1.8.2 build is compiled from).
    Not obtained by running tools/list — see deployment.verified.
  tool_groups:
    web_analysis: [core_web_vitals, security_headers, seo_audit, email_security, brand_assets, redirect_chain, indexability_checker, web_checker, email_verify, tech_stack, http_status_checker, favicon_checker, microservice_health_check, robots_txt_parser]
    developer_utilities: [regex_builder, yaml_validator, mock_jwt_generator, user_agent_analyzer, status_code_checker, swagger_docs_creator]
    wallet: [wallet_usage, wallet_set_cap]
    autonomously_built: 54 further security/DNS/TLS/subdomain/API-audit tools generated by the provider's "brain" loop (see tools_file)
- id: agentcontext
  name: agentcontext MCP server
  package: '@mbeato/agentcontext-mcp'
  version: 0.1.2
  published: '2026-04-29'
  registry: npm
  registry_url: https://www.npmjs.com/package/@mbeato/agentcontext-mcp
  transport: stdio
  bin: agentcontext-mcp
  install: npx -y @mbeato/agentcontext-mcp
  client_config:
    mcpServers:
      agentcontext:
        command: npx
        args: ['-y', '@mbeato/agentcontext-mcp']
  source_code: https://github.com/mbeato/agentcontext-mcp
  homepage: https://agentsmd.apimesh.xyz
  tool_count: 2
  tools:
  - name: read_agent_context
    description: Detect and read the agent-context rules files (AGENTS.md, CLAUDE.md, .cursor/rules, .clinerules, .windsurf/rules ...) in a repository.
    source: https://github.com/mbeato/agentcontext#mcp-server
  - name: convert_agent_context
    description: Convert agent-context rules between formats (the same conversion POST /normalize on agentsmd.apimesh.xyz performs).
    source: https://github.com/mbeato/agentcontext#mcp-server
  note: Tool names and purposes from the package README; input schemas not read (the package was not executed).