Skip to content

MCP servers › io.github.Bustlll › agent-data-api

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

io.github.Bustlll/agent-data-api

Memecoin screener, backtests, exit alerts, wallet traces + web search, enrichment, 50+ tools (x402) — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-24version 1.0.1streamable HTTP15 tools

Summary

io.github.Bustlll/agent-data-api is a remote MCP server listed in the official MCP registry at version 1.0.1. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 15 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
15
Last tested
2026-10-24

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-24
Mode
read-only (no tool calls)
Latest version
1.0.1, published 2026-10-23 (registry, as of the 2026-10-24 snapshot)
First listed version
2026-10-23 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-10-23; 2 in the 90 days before the 2026-10-24 snapshot.
Most recent 2 versions
  • 1.0.1 · 2026-10-23
  • 1.0.0 · 2026-10-23
(versions still listed in the registry only)
Registry data
snapshot 2026-10-24
Package and repository
checked 2026-10-24
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.0.1 (published 2026-10-23).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory
15tools
0resources
0prompts

None of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.

  • catalog_read

    “FREE, no payment.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • whatstringrequired“Which free answer to return.”
    • watchstring“memecoin_alerts: the watch id from memecoin_watch.”
    • sinceinteger“memecoin_alerts: return alerts after this cursor (default 0).”
  • “Search the web (DuckDuckGo via Cloudflare's network).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs, 1 required
    • qstringrequired“The query, e.g.”
    • readinteger“Pages to read in full (0 = results only, default 0).”
    • researchboolean“true = research mode: read up to 8 pages and return key passages ($0.05).”
    • regionstring“Country code for results, e.g.”
    • timestring“Only results from this period.”
    • limitinteger“Results to return in results-only mode (default 10).”
    • max_charsinteger“Max characters per page read (default 4000).”
  • “Fetch one public URL and return its main content as clean markdown (title, publish date, word count) plus a prompt-injection verdict; raw=true returns the raw body instead (text or base64).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs
    • urlstring“Public http(s) URL to read.”
    • rawboolean“true = raw body (no cleanup), default false.”
    • formatstring“raw mode only (default auto).”
    • max_charsinteger“Max characters returned (default 20000).”
    • textstring“Instead of url: text to scan for prompt injection.”
    • htmlstring“Optional HTML of that text, to also find hidden instructions.”
  • company_enrichon 1 other server

    “Everything public about a company from its domain: name, description, size hints, address, phones, emails, socials, website platform, email provider and security, SaaS stack.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • domainstringrequired“Company website domain, e.g.”
    • tierstring“Default standard.”
  • “Check email addresses without sending mail: syntax, domain and MX records, disposable domains, role accounts, catch-all hints, and a valid / risky / invalid verdict each, plus a summary.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • emailsarray or stringrequired“Addresses: a list, or one comma-separated string (max 200).”
  • “Check a token before trading.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • addressstringrequired“Token contract (0x...) or Solana mint.”
    • chainstring“Chain of a 0x token (Solana mints are detected).”
    • levelstring“Depth and price (default safety).”
  • address_checkon 1 other server

    “Screen a wallet address (BTC, ETH/EVM, Solana, Tron, XRP, LTC) against OFAC sanctions and scam lists with on-chain context.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • addressstringrequired“The wallet address.”
    • tierstring“Default standard.”
  • memecoin_screen

    “Run your own screen over the live market: every pump.fun launch from our real-time stream plus DEX pools on Solana and Base, 120+ fields in 5m-24h windows, 8 presets.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs
    • presetstring“Optional starting point.”
    • filtersobject“{field: condition}; added to the preset's filters (yours win).”
    • sortarray“Sort keys, e.g.”
    • chainsarray“Default both.”
    • sourcesarray“pump.fun = bonding curves from our real-time stream; dex = DEX pools.”
    • limitinteger“Max tokens returned (default 20).”
    • sincestring“Cursor from a previous response: only tokens created after it (for polling).”
  • memecoin_holder_trace

    “Are a token's early buyers independent or one operator?”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • tokenstringrequired“pump.fun mint or Base token 0x...”
    • tierstring“Default standard.”
    • buyersinteger“Standard tier: early buyers to trace (default 30).”
    • depthinteger“Standard tier: funding hops (default 2).”
  • memecoin_backtest

    “Replay a screen strategy plus exit rules on every graded pump.fun token we recorded (snapshots at 5/15/30/60 min of age) or on a preset's live signal ledger: win rate, average / median return after f…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs
    • strategyobject“A screen strategy.”
    • exitsobject“Exit rules (same names as memecoin_exit_check).”
    • entryAtinteger or string“Snapshot age in minutes (5, 15, 30, 60) or "signal" (a preset's live signals).”
    • sweepobject“Grid to sweep (max 64 combinations).”
    • costPctPerSidenumber“Fees + slippage per side in % (default 2).”
    • minVolumeUsd5mnumber“Skip tokens with less 5-minute volume at entry (default 500).”
    • daysnumber“Lookback in days (default 7, max 21).”
  • memecoin_exit_check

    “Your entry and exit rules applied to the token's real path since you entered: hold / sell X% / exit now, with every rule that fired and the position's gain, peak and drawdown.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs, 2 required
    • tokenstringrequired“Token mint / contract.”
    • chainstring“Optional; detected from the token.”
    • entryobjectrequired“Give ONE of: marketCapUsd, priceUsd or time (ISO 8601, e.g.”
    • rulesobject“Exit rules: everything in the backtest exits plus live-only signals.”
    • alreadySoldPctnumber“% of the original position already sold (for tiered take-profits).”
    • notifyAtGainPctarray“Watches only: alert once at each gain %, e.g.”
  • memecoin_watch

    “Creates a watch (this is the only tool that stores state): we re-run your screen strategy (alert on each new matching token) or your position's exit rules (alert when hold turns into sell / exit, plu…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    7 inputs, 1 required
    • typestringrequired“strategy = alert on new matching tokens; position = alert on exit signals.”
    • strategyobject“A screen strategy.”
    • positionobject“An open position to check.”
    • intervalstring“Check interval (default 5m).”
    • tierstring“Default standard.”
    • webhookstring“Optional https URL: each alert is POSTed there.”
    • notifyobject“Optional delivery of each alert as a message.”
Show 3 more tools
  • x402_lookup

    “Answers about the x402 agent-payments market from the whole Bazaar index and Base chain history.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    11 inputs, 1 required
    • actionstringrequired“Which question to answer (sets the price, see above).”
    • needstring“recommend: the task in plain words, e.g.”
    • max_pricenumber“recommend: max USD per call.”
    • networkstring“recommend: e.g.”
    • limitinteger“recommend / payments_feed: rows to return.”
    • urlstring“seller_check: endpoint URL, host or payTo address.”
    • addressstring“payer_profile / payments_feed: Base wallet 0x...”
    • sellerstring“seller_customers: seller host or payTo address.”
    • daysinteger“payer_profile / seller_customers: lookback days (default 30).”
    • depthinteger“payer_profile: hops (default 1).”
    • sincestring“payments_feed: ISO time cursor from the previous response.”
  • shopify_lookup

    “action=store: one Shopify store's apps by category (reviews, email, subscriptions, loyalty...), pixels, theme and catalog hints, gaps and sales pitch angles.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    8 inputs, 1 required
    • actionstringrequired“store = one store by domain; search = find stores in the index.”
    • domainstring“store: the store's domain, e.g.”
    • appstring“search: stores using this app, e.g.”
    • exclude_appstring“search: stores NOT using this app.”
    • missingstring“search: stores with no app in this category, e.g.”
    • countrystring“search: 2-letter country, e.g.”
    • qstring“search: keyword in the store name or products.”
    • limitinteger“search: rows (default 10).”
  • data_tool_run

    “Runs one data tool with its JSON input: Google Maps places with contacts, YouTube videos / transcripts / comments, Indeed, LinkedIn and 13 other job boards, LinkedIn companies, Google News and Trends…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • toolstringrequired“Tool id from catalog_read what=prices, e.g.”
    • inputobjectrequired“The tool's JSON input (see its example in catalog).”
    • tierstring“max = bigger caps, only for the tools listed above.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 77
Tools with a description
100% of 15
Typical description length
550 characters

The tool set

Counted from the listing

Tools
15
Size of the list
about 7,907 tokens for an agent to load (characters ÷ 4)
Naming
15 of 15 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://agent-data.centorprat.workers.dev/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "agent-data-api": {
      "url": "https://agent-data.centorprat.workers.dev/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "agent-data-api": {
      "type": "http",
      "url": "https://agent-data.centorprat.workers.dev/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"agent-data-api","type":"http","url":"https://agent-data.centorprat.workers.dev/mcp"}'
Claude Code
claude mcp add --transport http agent-data-api https://agent-data.centorprat.workers.dev/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://agent-data.centorprat.workers.dev/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint agent-data.centorprat.workers.dev/mcpSession openedmatchesour test · 2026-10-24
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-24

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.Bustlll/agent-data-api

Answered from the data above

Does io.github.Bustlll/agent-data-api need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.Bustlll/agent-data-api been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 2,054 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 15 tools, 0 resources, 0 prompts.
  4. 6,829 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-24; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-24
MCP capability
tools
our test · 2026-10-24
Transport
streamable HTTP
registry · 2026-10-24
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-24
Lifecycle status
registry · 2026-10-24
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Bustlll/agent-data-api: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.github.Bustlll/agent-data-api

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.Bustlll/agent-data-api)](https://protocolprobe.com/mcp/servers/io.github.Bustlll/agent-data-api)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology