NobleBlocks MCP Server (nobleblocks/nobleblocks-mcp) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 16 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
71/100

NobleBlocks MCP Server

Enables searching and exploring 340 million academic papers from 15+ databases with semantic search, citation graphs, and knowledge graph connections for biomedical entities.

→ nobleblocks/nobleblocks-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

nobleblocks

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
16 tools verified — handlers match their declared behaviour
8 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 6 credentials: NOBLEBLOCKS_API_KEY, NB_INTERNAL_TOKEN, DB_PASS, LENS_API_KEY, EPO_CONSUMER_KEY, EPO_CONSUMER_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configNOBLEBLOCKS_API_BASE
🔐 secretNOBLEBLOCKS_API_KEY"": "nb_pk_your_key_here"
configOAUTH_TABLE_NAME
configAWS_REGION
configAWS_DEFAULT_REGION
configMCP_BASE_URL
configCONSENT_PAGE_URL
configLOG_LEVELINFO Logging verbosity
🔐 secretNB_INTERNAL_TOKEN
configMCP_HOST
configMCP_PORT
configMCP_VERSION
configRATE_LIMIT_TRIAL
configRATE_LIMIT_FREE
configRATE_LIMIT_PRO
configRATE_LIMIT_PER_MINUTE
configAUDIT_LOG_FILE
configDB_HOST
configDB_PORT
configDB_NAME
configDB_USER
🔐 secretDB_PASS
🔐 secretLENS_API_KEY
🔐 secretEPO_CONSUMER_KEY
🔐 secretEPO_CONSUMER_SECRET
// quality suggestions

Tool annotations

8/16 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

8/16 tools missing one or more hints — search_papers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_paper (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); find_similar (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool handlers catch errors

7/8 tool handlers wrap calls in try/catch (88%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/nobleblocks/nobleblocks-mcp)](https://m8ven.ai/mcp/nobleblocks/nobleblocks-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c54a6386306708cbc4029e9da9bf39e602165484
code hash: 06cef94828d6ed2738a535e6e0aa0c13cb36dba0e6e48097f7ea41f65d7d9c5d
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client