@svgrid/mcp

MCPcommunitylive
v3.0.1com.svgridMITUpdated 1mo agonpmGitHub

Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.

Endpoint healthlive
checked 3 days ago · 157ms
100% of the last 5 checks 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 →
820Downloads/wk
177GitHub stars
8Forks
1mo agoLast update
Package
Authorcom.svgrid
LicenseMIT
Version3.0.1
Sourcenpm+mcp-registry
npm@svgrid/mcp
GitHubsv-grid/sv-grid
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 surface33 tools · 3 privileged
Security scan✓ Cleanv2.3.3 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 20, 2026

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

Tools

33 tools · 3 privileged
Statically extracted from the published packagev2.3.3 · 1mo 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.

list_examplesNo description published

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

get_example_sourceNo description published

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

list_docsNo description published

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

get_docNo description published

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

search_docsNo description published

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

get_api_referenceNo description published

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

introspect_sourceNo description published

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

scaffold_entityNo description published

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

studio_new_projectNo description published

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

studio_load_projectNo description published

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

studio_describe_projectNo description published

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

studio_get_configNo description published

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

studio_capabilitiesNo description published

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

studio_add_entityNo description published

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

studio_add_screenNo description published

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

studio_add_blockNo description published

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

studio_add_componentNo description published

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

studio_update_blockNo description published

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

studio_remove_blockprivilegedNo description published

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

studio_move_blockprivilegedNo description published

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

studio_update_screenNo description published

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

studio_remove_screenprivilegedNo description published

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

studio_set_screen_layoutNo description published

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

studio_set_entity_sourceNo description published

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

studio_set_themeNo description published

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

studio_set_accessNo description published

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

studio_set_authNo description published

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

studio_set_data_layerNo description published

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

studio_set_tenancyNo description published

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

studio_set_jobNo description published

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

studio_set_deploy_targetNo description published

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

studio_validateNo description published

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

studio_generate_appNo description published

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

0 of 33 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

Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

33 tools · 3 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

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