io.github.orcar-studio/fascia-mcp-server

MCPcommunity
v0.1.1io.github.orcar-studioUnknownUpdated 7mo agonpmGitHub

Expose Fascia-deployed Tools and Entity schemas to AI agents via MCP

MCP (Model Context Protocol) server for Fascia - expose your deployed Tools and Entity schemas to AI agents like Claude, Cursor, and other MCP-compatible clients. This server connects to your Fascia workspace and exposes: Tools - All HTTP-triggered Tools become callable MCP tools (with risk level annotations) Resources - Entity schemas, Tool specs, and workspace metadata available as MCP…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). 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 →
7mo agoLast update
Package
Authorio.github.orcar-studio
LicenseUnknown
Version0.1.1
Sourcemcp-registry
npm@fascia-run/mcp-server
GitHuborcar-studio/fascia
SBOMCycloneDX 1.6 ↓
Trust Status
B
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—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv0.1.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

No tool declarations found in the source3mo ago

Forge read 10 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

MCP (Model Context Protocol) server for Fascia - expose your deployed Tools and Entity schemas to AI agents like Claude, Cursor, and other MCP-compatible clients. This server connects to your Fascia workspace and exposes: Tools - All HTTP-triggered Tools become callable MCP tools (with risk level annotations) Resources - Entity schemas, Tool specs, and workspace metadata available as MCP resources Set your Fascia API key as an environment variable: Get your API key from fascia.run/app/settings…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.