@scope-bid/scope-claims-mcp

Name: @scope-bid/scope-claims-mcp
Author: bid.scope

MCPcommunitylive

v1.0.9bid.scopeApache-2.0Updated 29d agonpm GitHub

Insurance claims-side vendor procurement (IMEs, IA, surveillance). Preview - V2 launches Q3 2026.

Endpoint healthlive

checked 2 days ago · 195ms · auth required

100% of the last 1 check reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

29d agoLast update

Package

Authorbid.scope

LicenseApache-2.0

Version1.0.9

Sourcenpm+mcp-registry

npm@scope-bid/scope-claims-mcp

GitHubscope-bid/scope-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

ProvenanceAttested · unverified by Forge

Dependencies59 resolved · 1 with advisories

Tool surface4 tools · none privileged

Security scan✓ Cleanv1.0.9 · 19d agoHow well does this scan work?

MODERATE@hono/node-server@1.19.17Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`) · transitive

EvalsNone

IndexedJul 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged

Statically extracted from the published packagev1.0.9 · 19d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

scope_claims_statusNo description published

This tool published no description. Forge does not invent one.

scope_claims_categoriesNo description published

This tool published no description. Forge does not invent one.

scope_claims_join_waitlistNo description published

This tool published no description. Forge does not invent one.

scope_reschedule_projectNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Insurance claims-side vendor procurement (IMEs, IA, surveillance). Preview - V2 launches Q3 2026.

Keywords

mcp

Alternatives

Comparing tool surfaces…

@scope-bid/scope-claims-mcp

Tools

Tools exposed

No dependency coverage