A-

pypi:nexustoken-sdk

https://pypi.org/project/nexustoken-sdk/
92/100 · MCP Trust Grade · checked 4h ago · MCP 0.6.6

What it offers — 12 tools · AI & ML

nexus_create_task
nexus_check_status
nexus_discover_capabilities
nexus_create_job
nexus_check_job
nexus_accept_job
nexus_reject_job
nexus_dispute_job
nexus_claim_job
nexus_submit_job
nexus_register_spec
nexus_backfill_specs
Spec / packaging20%100
Security (OWASP MCP)30%90
Maintenance / popularity20%100
Tool hygiene15%80
Transparency / provenance15%85

Findings

INFO Static analysis of PyPI package nexustoken-sdk@0.6.6 (source: github.com/bobuilds/nexustoken-sdk) — stdio server, no remote endpoint. Runtime behavior not measured.
Grade another server

We re-grade pypi:nexustoken-sdk on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — pypi:nexustoken-sdk grade A-
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade A- · wmcp.sh
[![MCP Trust Grade A-](https://wmcp.sh/mcp/grade/pypi%3Anexustoken-sdk/badge.svg)](https://wmcp.sh/mcp/grade/pypi%3Anexustoken-sdk)
<a href="https://wmcp.sh/mcp/grade/pypi%3Anexustoken-sdk"><img src="https://wmcp.sh/mcp/grade/pypi%3Anexustoken-sdk/badge.svg" alt="MCP Trust Grade A- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.