Academic Research MCP Server
https://nexgendata-mcp-proxy.steve-corbeil.workers.dev
Registry code: a1951ed3136c1b0b
B2B sales intelligence — company emails, enrichment, lead lists, hiring & funding signals.
from a public catalogue that lists it, not from the operator
- endpoint
- https://nexgendata-mcp-proxy.steve-corbeil.workers.dev/academic-research-mcp-server/mcp
- protocol
- http-sse ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Academic Research MCP Server live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is Academic Research MCP Server free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does Academic Research MCP Server have?
- 2 tools: search_google_scholar, search_arxiv.
- Is Academic Research MCP Server safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.8%· all time 99.8%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- used for
- search arxiv papers
- search google scholar for papers
- takes → gives
- text → data
- tools
- 2 reads
- note
- resells another provider
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search_google_scholar reads auth-required 7h ago
Query Google Scholar for academic papers, citations, and research articles across all disciplines. Returns paper title, authors, publication venue, citation count, abstract preview, and full-text link if available. Use for comprehensive literature searches, citation tracking, or finding highly-cited works.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Search terms or research topic (e.g. 'machine learning bias', 'climate change economics', 'gene therapy advances')" }, "max_results": { "type": "integer", "default": 10, "description": "Maximum papers to retrieve (default 10, recommended for focused results)" } } }arguments 17 linessearch_arxiv reads auth-required 7h ago
Search the arXiv preprint repository for peer-reviewed academic papers in physics, mathematics, computer science, and related fields. Returns paper title, author list, abstract, publication date, PDF link, and category classification. Use for cutting-edge research, literature review, or staying current in academic fields.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Research keywords or topic (e.g. 'neural networks', 'quantum computing', 'protein folding')" }, "max_results": { "type": "integer", "default": 10, "description": "Number of papers to return (default 10, higher values for comprehensive literature review)" } } }arguments 17 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida1951ed3136c1b0b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a1951ed3136c1b0b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a1951ed3136c1b0b?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.