GhOsT77 crypto data jobs
MCP server · ghost77-agent.onrender.com · found in a public list · checked since 2026-11-01
Live, handshake completed · latest check
Read-only crypto tools for token risk, Hyperliquid data and Base network status.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Check a token before trading: Check a token address for rug-pull, honeypot, tax and holder-concentration risks.
https://ghost77-agent.onrender.com/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
2 passed, 0 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-11-01 | 2 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-11-01 | 2 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
acp_agent_repair_checkbase_protocol_healthbridge_route_checkcontract_researchcontract_security_scancrypto_news_digestdaily_bundlefunding_arb_scangas_fee_timingghost_web_scraperhl_funding_snapshothl_liquidation_maphl_quick_trade_ideahl_smart_moneyhl_top_movershl_trader_copy_checkmarket_scan_reportposition_health_checkproject_research_reportprotocol_stats_snapshotrug_honeypot_quick_checksentiment_alphatoken_due_diligencetoken_technical_analysistoken_unlock_calendartrade_strategy_consultwallet_watch_alert
- Tools
- 27
- This list since
- 2026-11-02
- First listed to us
- 2026-11-01
- List changes, 90 days
- 1
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- tools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
crypto_news_digest timeframe* tokens topichl_funding_snapshot marketsentiment_alpha includeX query*protocol_stats_snapshot protocol*ghost_web_scraper output_format request* url*hl_top_movers limit window*token_due_diligence chain* tokenAddress*base_protocol_health blocks* chain*market_scan_report focusbridge_route_check bridge_amount bridge_token* from_chain* to_chain*project_research_report chain project*contract_research chain* contractAddress*
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Financial and economic data / Crypto and on-chain data / Token, contract and wallet risk checks / Check a token before trading (primary); Financial and economic data / Crypto and on-chain data / Gas and network fees. Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-11-01. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 313 ms |
cloudflare:EWR |
Live, handshake completed HTTP 200 | 530 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_013a8cce379731d2