io.github.trustscoreagent/mcp-server
NPM · @TRUSTSCOREAGENT/MCP-SERVER · SCANNED AUG 5
Check the reputation of AI microservices and public APIs from an open trust registry.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 24 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 430 tokens (~143/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @trustscoreagent/mcp-server
claude mcp add trustscoreagent-mcp-server -- npx -y @trustscoreagent/mcp-server
codex mcp add trustscoreagent-mcp-server -- npx -y @trustscoreagent/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trustscoreagent-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@trustscoreagent/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add trustscoreagent-mcp-server --command npx --arg -y --arg @trustscoreagent/mcp-server
mcp_servers:
trustscoreagent-mcp-server:
command: "npx"
args: ["-y", "@trustscoreagent/mcp-server"] {
"mcpServers": {
"trustscoreagent-mcp-server": {
"command": "npx",
"args": [
"-y",
"@trustscoreagent/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 3 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: Apache-2.0 functional
- 2 Aug 26 −1
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Aug 2026 · Analysed npm/@trustscoreagent/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_reputation ~114
Check the trust score and reputation of an AI microservice before calling it. Returns a score between 0 and 1, confidence level, number of ratings, and dimensional breakdown (availability, latency, conformity). Use this BEFORE calling any untrusted external service to verify its reliability.
| Name | Type | Req | Description |
|---|---|---|---|
| service_did | string | yes | The service to check. Accepts any format: URL (https://api.example.com), domain (api.example.com), or DID (did:web:api.example.com). All resolve to the same service. |
No output schema declared.
No examples provided.
list_services ~109
List AI microservices that have been rated, sorted by trust score. Use this to discover reliable services or find alternatives. Returns a paginated list with scores and dimensional breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Number of results (default 20, max 100) |
| min_ratings | number | — | Minimum number of ratings filter |
| min_score | number | — | Minimum trust score filter (0.0-1.0) |
| sort_by | string | — | Sort field (default: score) |
No output schema declared.
No examples provided.
submit_rating ~207
Rate an AI microservice after calling it. Provide the technical metrics from your interaction. This helps other agents know if the service is reliable. Include the receipt from the X-Trust-Receipt header if the service provided one.
| Name | Type | Req | Description |
|---|---|---|---|
| latency_ms | number | yes | Response time in milliseconds (round sub-millisecond responses up to 1) |
| quality_score | number | — | Subjective quality rating from 1 (poor) to 5 (excellent) (optional) |
| receipt | string | — | JWT receipt from the service's X-Trust-Receipt header (optional) |
| response_size_bytes | number | — | Size of the response in bytes (optional) |
| schema_valid | boolean | — | Whether the response matched the expected format (optional) |
| service_did | string | yes | The service you called. URL, domain, or DID (e.g., api.example.com) |
| status_code | number | yes | HTTP status code returned by the service (e.g., 200, 500) |
No output schema declared.
No examples provided.