Lowdown MCP Lookup

    1

    Before you choose or connect to an MCP server, see its Registry declaration and 30 days of daily observations.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Lowdown MCP Lookup

    Example session with this skill installed

    I'm thinking of connecting the MCP server mcp:ai.agent-bev/bev-door. Has it been responding lately, does it match what the Registry declares, and did its tools change?

    • Read your context and instructions
    • Compiled the lowdown mcp lookup

    Lowdown record for mcp:ai.agent-bev/bev-door (as of 2026-10-20)

    Summary: listed in the official MCP Registry, observed every day since 2026-10-06 with no missing days, and the observed version matches the declared one. No agent-reported interactions yet.

    Registry declaration

    FieldValue
    Listedyes (active)
    Declared version0.2.5
    Remote hostmcp.bev-buyer.ai
    Changes in the last 30 daysnone

    Recorded from Lowdown's first Registry snapshot (2026-10-19), so the first-recorded date is not when the server first appeared in the Registry.

    Daily observations (last 14 days)

    DaysReach levelHTTP statusTool countTools changed
    2026-10-06 to 2026-10-19 (14 of 14)2 (initialize + tools/list)2009no
    • Missing days: none
    • Server version observed: 0.2.5 (declared: 0.2.5)
    • Host observed: mcp.bev-buyer.ai (declared: mcp.bev-buyer.ai)

    How this was observed

    One POST initialize and one tools/list per day from a single location (GitHub Actions); no tool calls and no authentication. These are dated single probes, not uptime and not a score.

    Next steps

    • If you connect it, the tool list should have 9 tools, as observed on 2026-10-19.
    • Check again before relying on it later: the record updates daily.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Look up what has been recorded about an MCP server before you choose or connect to it.

    Lowdown keeps a daily record of the official MCP Registry and observes a fixed sample of 5,000 Registry servers every day (initialize and tools/list only; it never calls a tool or authenticates). This skill reads that record through one public, read-only GET endpoint. No API key, and nothing is sent except the server name.

    What you get for a server

    • Registry declaration: declared version, status, remote hosts, and changes in the last 30 days
    • Daily observations for the last 30 days: reach level, HTTP status, tool count, tool-schema changes
    • Missing days: days without an observation and the recorded reason
    • Tool names returned by tools/list
    • Declared vs observed: declared version and hosts next to the observed ones

    What it is not

    These are dated facts with their sources, not scores or rankings. A 401 is reported as a 401 (auth required), not as a failure. Each observation is a single probe from one location, not uptime.

    The underlying data is open (CC BY 4.0): https://github.com/PetShopBros/lowdown-data

    Daily observations cover a fixed sample of 5,000 Registry entries with a streamable-http remote; stdio-only servers are not probed. Each observation is one probe per day from a single location, not uptime. Tool names are recorded from 2026-10-20.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 25 days ago

    • Free with an Agensi account

    Permissions

    Network Access

    Network access: one public, read-only HTTPS GET to lowdown-proxy.vercel.app per lookup. No credentials, no files, no shell.

    Listed28 days ago
    Updated25 days ago

    What's inside

    Frequently Asked Questions

    For an MCP server name: the Registry declaration Lowdown recorded (version, status, remote hosts, and changes in the last 30 days) and, for servers in the observed sample, one entry per day for the last 30 days with reach level, HTTP status, tool count, tool-schema changes, the tool names, and any days without an observation with the recorded reason.

    Recorded data from a public API. The Registry record is updated once a day, and each sampled server is probed once a day, so every fact comes with its date.

    No. The skill uses one public, read-only GET endpoint with no key. Only the server name is sent.

    A fixed sample of 5,000 MCP Registry entries with a streamable-http remote (2,000 before 2026-10-19). Other Registry entries still get the Registry record; a server outside the sample returns observed: false, which says nothing about its status.

    No. Each observation is a single initialize and tools/list probe per day from one location (GitHub Actions). A 401 is reported as a 401 (auth required), not as a failure. Lowdown does not score, grade, or rank servers.

    Yes. The daily files are published under CC BY 4.0 at https://github.com/PetShopBros/lowdown-data, with a manifest of row counts and SHA-256 hashes.

    New in LLM Ops