io.github.cmdenney/logicnodes-mcp-bridge
NPM · @LOGICNODEZ/MCP-BRIDGE · SCANNED SEP 22
Signed PII-Shield: redact PII to an EIP-191 attestation, plus x402 pay-per-call agent tools.
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. 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 (MIT).Pass
- Actively maintained (last published 95 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 872 tokens (~96/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.cmdenney/logicnodes-mcp-bridge server?
io.github.cmdenney/logicnodes-mcp-bridge runs locally as an npm package, launched with npx -y @logicnodez/mcp-bridge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @logicnodez/mcp-bridge
claude mcp add cmdenney-logicnodes-mcp-bridge -- npx -y @logicnodez/mcp-bridge
{
"mcpServers": {
"cmdenney-logicnodes-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"@logicnodez/mcp-bridge"
]
}
}
} {
"servers": {
"cmdenney-logicnodes-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"@logicnodez/mcp-bridge"
]
}
}
} codex mcp add cmdenney-logicnodes-mcp-bridge -- npx -y @logicnodez/mcp-bridge
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cmdenney-logicnodes-mcp-bridge": {
"type": "local",
"command": [
"npx",
"-y",
"@logicnodez/mcp-bridge"
],
"enabled": true
}
}
} openclaw mcp add cmdenney-logicnodes-mcp-bridge --command npx --arg -y --arg @logicnodez/mcp-bridge
mcp_servers:
cmdenney-logicnodes-mcp-bridge:
command: "npx"
args: ["-y", "@logicnodez/mcp-bridge"] {
"McpServers": {
"cmdenney-logicnodes-mcp-bridge": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@logicnodez/mcp-bridge"
]
}
}
} assistant mcp add cmdenney-logicnodes-mcp-bridge -t stdio -c npx -a -y @logicnodez/mcp-bridge
{
"mcpServers": {
"cmdenney-logicnodes-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"@logicnodez/mcp-bridge"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Analysed npm/@logicnodez/mcp-bridge@1.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
logicnodes_compliance_sentry ~105
Autonomous regulatory attestation for agent transactions. Checks action against MiCA, EU AI Act, and US EO compliance rules. Returns attestation hash and compliance score. Cost: $0.01 USDC per check.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | Type of agent action (transfer, inference, governance, trade) |
| amount_usd | number | – | Transaction value in USD if applicable |
| jurisdiction | string | – | Regulatory jurisdiction (EU, US, GLOBAL) |
No output schema declared.
No examples provided.
logicnodes_escrow_verifier ~73
On-chain escrow state verifier. Checks LogicNodesEscrow contract for active escrow, balance, and release conditions. Cost: $0.001 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | Escrow ID or transaction hash |
| party_address | string | – | Address to check escrow for |
No output schema declared.
No examples provided.
logicnodes_gas_oracle ~74
Real-time Base mainnet gas price oracle. Returns current base fee, priority fee, and EIP-1559 deviation from 7-day average. Cost: $0.0001 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| percentile | number | – | Fee percentile (50, 75, 95, 99) |
No output schema declared.
No examples provided.
logicnodes_identity_register ~82
Register an agent identity on Base mainnet via AgentIdentityRoot. Returns on-chain identity hash and registration transaction. Cost: $0.01 USDC per registration.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Agent wallet address |
| capabilities | array | yes | List of agent capability strings |
| metadata_uri | string | – | IPFS or HTTPS URI for agent metadata |
No output schema declared.
No examples provided.
logicnodes_inference_attest ~101
Attest an AI inference result on-chain via InferenceAttestationNetwork. Produces a signed POL receipt verifiable by any chain participant. Cost: $0.001 USDC per attestation.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | Model confidence 0-1 |
| input_hash | string | yes | keccak256 of inference input |
| model_id | string | yes | – |
| output_hash | string | yes | keccak256 of inference output |
No output schema declared.
No examples provided.
logicnodes_peg_monitor ~62
USDC peg stability monitor. Returns current USDC/USD deviation, Circle reserve attestation status, and depeg risk score. Cost: $0.0001 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| threshold_bps | number | – | Alert threshold in basis points |
No output schema declared.
No examples provided.
logicnodes_pii_shield ~210
FLAGSHIP. Redact PII from text and get an EIP-191-signed attestation binding input_sha256 -> output_sha256 (prove WHAT was redacted without ever seeing the raw PII). Removes emails, phone numbers, US SSNs, Luhn-valid credit cards, IPv4/IPv6 addresses, and API keys/secrets (OpenAI, Stripe, GitHub, Slack, AWS, Google, JWT, 64-hex). Raw PII is NEVER returned or stored. $0.05 USDC per call via x402: pay USDC to the treasury shown in the 402 challenge, then retry with the X-Payment-Tx header. Verify the signature with EIP-191 ecrecover against signer 0x0D12B2B82e4aE84A15a032C31C6A8a23520Ecde7.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | the text to scan and redact PII from |
No output schema declared.
No examples provided.
logicnodes_sig_verify ~74
Cryptographic signature verification on Base. Verifies EIP-712 typed data signatures and returns signer address with on-chain proof. Cost: $0.0001 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_signer | string | – | Optional expected signer address |
| message | string | yes | – |
| signature | string | yes | – |
No output schema declared.
No examples provided.
logicnodes_zk_compute_attest ~91
Zero-knowledge compute attestation. Proves a computation was performed correctly without revealing inputs. Returns ZK proof hash anchored to Base via LogicNodesGraphCommitment. Cost: $0.05 USDC per proof.
| Name | Type | Req | Description |
|---|---|---|---|
| circuit_id | string | yes | ZK circuit identifier |
| computation_hash | string | yes | Hash of the computation to attest |
| public_inputs | array | – | – |
No output schema declared.
No examples provided.
What is the io.github.cmdenney/logicnodes-mcp-bridge server?
io.github.cmdenney/logicnodes-mcp-bridge is listed in the public MCP registry as io.github.cmdenney/logicnodes-mcp-bridge. Signed PII-Shield: redact PII to an EIP-191 attestation, plus x402 pay-per-call agent tools. This page covers its npm package (@logicnodez/mcp-bridge).
Is the io.github.cmdenney/logicnodes-mcp-bridge server safe to use?
io.github.cmdenney/logicnodes-mcp-bridge scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cmdenney/logicnodes-mcp-bridge server expose?
io.github.cmdenney/logicnodes-mcp-bridge exposes 9 tools: logicnodes_pii_shield, logicnodes_gas_oracle, logicnodes_sig_verify, logicnodes_peg_monitor, logicnodes_escrow_verifier, and 4 more. Their descriptions and schemas cost roughly 872 tokens of context every time the server is loaded.
Is the io.github.cmdenney/logicnodes-mcp-bridge server still maintained?
io.github.cmdenney/logicnodes-mcp-bridge is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.cmdenney/logicnodes-mcp-bridge server under?
io.github.cmdenney/logicnodes-mcp-bridge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.