# io.github.springrolldev/springroll

Register, deploy, review, and govern internal applications built with coding agents.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.0
- **Author:** io.github.springrolldev
- **License:** Unknown
- **Endpoints:** streamable-http https://springroll.dev/api/mcp
- **Source:** https://springroll.dev/api/mcp
- **Endpoint health:** reachable (last checked 2026-09-25T12:15:21.859Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 10 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-25T12:15:21.859Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

15 declared. Observed from a live `tools/list` probe.
- `springroll.context` — Returns the organization, identity, and permissions this agent token acts as, together with the deployment runtimes configured for it. Call this first: it tells
- `springroll.deploy` — Registers the project if it is new, attaches whatever source you give it, and deploys it using the application's Deployment workflow. Direct applications go to 
- `springroll.deploy.status` — Returns a deployment's current status, refreshing it from the runtime provider when the build is still in progress. Statuses: QUEUED, VALIDATING, BUILDING, DEPL
- `springroll.deploy.promote` — Promotes a tested deployment into the next environment (development -> uat, uat -> production). Reuses the already-built artifact rather than rebuilding, so the
- `springroll.placement.preview` — Scores where SpringRoll would place this application and what it would cost, without deploying or writing anything. It shares its implementation with springroll
- `springroll.app.get` — Returns an application's registry record: metadata, lifecycle stage, risk score, and whichever of the optional sections you ask for. No secrets are included. Se
- `springroll.app.list` — Lists applications in this organization, newest first. Use `search` to find one by name or slug.
- `springroll.app.update` — Updates App Portal metadata: description, icon, tags, department, support contact, and data classification. Visibility is deliberately not editable here, becaus
- `springroll.approval.submit` — Submits an approval request of any supported type: UAT_PROMOTION, UAT_SIGN_OFF, PRODUCTION_PROMOTION, VISIBILITY_CHANGE, OWNERSHIP_TRANSFER, RETIREMENT, DOMAIN_
- `springroll.approval.get` — Returns an approval request with its assigned reviewers, decisions so far, and the policy snapshot taken at submission. Poll this to find out whether a release 
- `springroll.policy.check` — Reports which governance policies an application would pass or fail for an environment. Send `manifest` (YAML or JSON) to validate a document without creating a
- `springroll.connect.data_products` — Without `dataProduct`, lists the governed data products this organization publishes: what each one holds, who owns it, and how sensitive it is. With `dataProduc
- `springroll.connect.request_access` — Requests access to a data product for one environment, naming the exact fields the application needs. A data owner must approve, and may narrow the field list o
- `springroll.connect.access_status` — Returns the status of a data access request: REQUESTED, APPROVED, REJECTED, REVOKED, or EXPIRED, with the fields actually approved. Approved fields are often na
- `springroll.app.record_prompts` — Attaches the conversation that produced this application to its record, as reference for whoever maintains it next and for the reviewer who has to approve it. A

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"springroll\": {\n      \"type\": \"http\",\n      \"url\": \"https://springroll.dev/api/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.springrolldev%2Fspringroll
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.springrolldev%2Fspringroll/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.springrolldev%2Fspringroll
- HTML page: https://forgeregistry.com/registry/io.github.springrolldev%2Fspringroll
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.