Xbrl Api Minimal MCP Server

xbrl-api-minimal npm v7.0.0

Published by an unidentified publisher — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
F
57/100
Last scanned
Trust
F · 57/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
F Why this grade 100 − 42.8 = 57/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−40.7 Hardcoded JSON Web Token in server code ×4 MTC-SRC-008 exfiltration
−2.1 Package has no source repository MTC-SUP-011 supply-chain

Grade capped: 4 confirmed high findings → grade capped at D. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind the deduction.

Findings 8

high Hardcoded JSON Web Token in server code (supabase/functions/api-key-tester/index.ts)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `supabase/functions/api-key-tester/index.ts:28`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: JSON Web Token: eyJh…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server supabase/functions/api-key-tester/index.ts

high Hardcoded JSON Web Token in server code (supabase/functions/api-key-validator/index.ts)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `supabase/functions/api-key-validator/index.ts:28`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: JSON Web Token: eyJh…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server supabase/functions/api-key-validator/index.ts

high Hardcoded JSON Web Token in server code (supabase/functions/keys_issue/index.ts)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `supabase/functions/keys_issue/index.ts:28`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: JSON Web Token: eyJh…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server supabase/functions/keys_issue/index.ts

high Hardcoded JSON Web Token in server code (supabase/functions/v1_filings/index.ts)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `supabase/functions/v1_filings/index.ts:28`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: JSON Web Token: eyJh…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server supabase/functions/v1_filings/index.ts

medium Hardcoded egress to an external endpoint (app/docs/DocsContent.tsx)MTC-SRC-003

In the server's implementation (`app/docs/DocsContent.tsx:15`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: requests.get( "https://api.example.com/v1/companies/7203"

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server app/docs/DocsContent.tsx

medium Hardcoded egress to an external endpoint (app/forgot-password/page.tsx)MTC-SRC-003

In the server's implementation (`app/forgot-password/page.tsx:24`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://readdy.ai/api/form/d33so10ahuop1eu2ivig'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server app/forgot-password/page.tsx

medium Hardcoded egress to an external endpoint (app/sdk/page.tsx)MTC-SRC-003

In the server's implementation (`app/sdk/page.tsx:30`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://api.xbrl.jp/v1/companies'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server app/sdk/page.tsx

low Package has no source repositoryMTC-SUP-011

"xbrl-api-minimal" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package xbrl-api-minimal

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v7.0.0 latest F 57/100 8 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: F · 57/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/xbrl-api-minimal/badge.svg)](https://mcptrustchecker.com/registry/xbrl-api-minimal)
HTML
<a href="https://mcptrustchecker.com/registry/xbrl-api-minimal"><img src="https://mcptrustchecker.com/registry/xbrl-api-minimal/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/xbrl-api-minimal/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan xbrl-api-minimal --online

Use the free API → How scoring works

More in Finance & Commerce