All servers / Developer / Effected MCP server
Effected MCP server
The effected-mcp server: the tool's MCP tools on the kit's MCP boundary
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 0.18.5. Package: @effected/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (28.2 seconds including download)
- Tools offered: 7
- Last published: 2026-11-16
- Weekly downloads (npm): 1,918
- License: MIT · Direct dependencies: 7
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
identityno parametersReports the effected tool's identity: the tool name, this server's version, the carrier distribution it was launched through (null for a direct install), and the resolved effect version.
schema_check4 of 4 parameters describedChecks the generated schema documents against the config, writing nothing. Drift and staleness arrive as the result's verdict, with each changed document's full diff; they are not errors. Reloads the config on every call.
schema_build4 of 4 parameters describedGenerates the schema documents and catalogs the config declares and writes the ones that changed, wherever the config puts them. A refused drift or a failed gate writes nothing and arrives as the result's verdict. Reloads the config on every call.
schema_validate3 of 3 parameters describedValidates a JSON payload file against a local schema document, with each finding's line and column. A payload that does not conform is valid: false, not an error.
package_build2 of 2 parameters describedBuilds one package from its effected.toml into dist/prod: JS, declarations, the manifest, the API model and any binary. A build that crashes or records an error arrives as the result's verdict "failed" with its issues, not as an error. Reloads the config on every call.
action_build3 of 3 parameters describedBuilds one GitHub Action from the [action] table of its effected.toml into dist: validates the config and action.yml, bundles each entry into one file, and checks that each loads. It writes only dist unless persist is true, which also copies the build to .github/actions/local and generates .actrc and .github/workflows/act-test.yml. Validation stopping the build or an entry failing arrives as the result's verdict "failed", not as an error. Reloads the config on every call. The load check imports each bundle, which runs an action with no GITHUB_ACTIONS guard unless [action.build] importCheck is false; a worker's own table can set importCheck = false to skip that worker alone.
action_init4 of 4 parameters describedScaffolds a new GitHub Action in a package directory: the [action] table of effected.toml, action.yml, src/main.ts, src/program.ts and tsconfig.json, to the kit's canonical shape, ready for action_build. It refuses, writing nothing, when any of those files exists, unless force is true, and always when a path it writes is a symbolic link or the wrong kind of entry: it never follows a link and never writes outside cwd. It edits no package.json: the result names the dependencies to add and whether the package is type module.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.