reactor-mcp-server@1.3.10
VERIFIED· not startedPublisher claims: "An extensible MCP server built on Reactor: tools are contributions, and a contribution can be extended" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
REACTOR_MCP_OAUTH_ISSUERREACTOR_MCP_OAUTH_JWKS_URIREACTOR_MCP_OAUTH_REQUIRED_SCOPESREACTOR_MCP_OAUTH_RESOURCEREACTOR_MCP_OAUTH_SCOPESor--oauth-resource/--oauth-issuer/--oauth-jwks-uri/--oauth-scopes/--oauth-required-scopesConfiguration, not credentials: REACTOR_MCP_HOST, REACTOR_MCP_LOG, REACTOR_MCP_NAME, REACTOR_MCP_PATH, REACTOR_MCP_PORT, REACTOR_MCP_TOOLSETS, REACTOR_MCP_TRANSPORT- Where it talks to
- no vendor host named in the codeAlso datalayer.run — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names datalayer.run as well as its own vendor. The guard injects REACTOR_MCP_OAUTH_ISSUER, REACTOR_MCP_OAUTH_JWKS_URI, REACTOR_MCP_OAUTH_REQUIRED_SCOPES, REACTOR_MCP_OAUTH_RESOURCE, REACTOR_MCP_OAUTH_SCOPES only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.3.7
vet-skills diff reactor-mcp-server 1.3.7 1.3.10This version reaches for something 1.3.7 did not: 5 new credential variables (REACTOR_MCP_OAUTH_ISSUER, REACTOR_MCP_OAUTH_JWKS_URI, REACTOR_MCP_OAUTH_REQUIRED_SCOPES, REACTOR_MCP_OAUTH_RESOURCE, …). Compared from the two recorded runs, not from source.
- New credential variables
- REACTOR_MCP_OAUTH_ISSUER, REACTOR_MCP_OAUTH_JWKS_URI, REACTOR_MCP_OAUTH_REQUIRED_SCOPES, REACTOR_MCP_OAUTH_RESOURCE, REACTOR_MCP_OAUTH_SCOPES
1.3.7 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 95/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
No findings across 5,896 lines in 20 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for reactor-mcp-server@1.3.10 as of 10 h ago. This is the package itself, not its dependencies.