Finds real, maintained open-source repos that fit your project. MCP grounding for coding agents.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://code-synapse-mcp.leewaystudio.com/mcp2 tools · 186msfind_fit_candidatesPre-adoption decision tool for open-source reuse. Call BEFORE implementing non-trivial functionality that a maintained OSS component could provide (queue, scheduler, parser, auth, cache, protocol client, ...) or before adding a dependency. Send a short capability need plus your project's minimal co…Pre-adoption decision tool for open-source reuse. Call BEFORE implementing non-trivial functionality that a maintained OSS component could provide (queue, scheduler, parser, auth, cache, protocol client, ...) or before adding a dependency. Send a short capability need plus your project's minimal co…
| Parameter | Type | Description |
|---|---|---|
| need* | string | Capability need, e.g. "job queue with retry for node.js". No project names, paths, or secrets. |
| constraints | object | Minimal project constraints. Each verdict comes back as pass|fail|unknown per candidate. |
| existing_components | array | owner/repo you already use — excluded and counted as already_have |
| exclusions | array | — |
| max_candidates | integer | — |
| telemetry | — | aggregate stores zero user text (outcome counters only); debug also stores the need for 30 days |
| strict | boolean | also exclude candidates whose required constraint fields are unknown |
search_componentsDeprecated: for all new integrations use find_fit_candidates instead. Compatibility-only free-text keyword search over the same corpus (GitHub repos with >=2000 stars), WITHOUT constraint checking or pass/fail verdicts. Returns up to 12 candidates with signals (role, protocols, affordance, fit, fre…Deprecated: for all new integrations use find_fit_candidates instead. Compatibility-only free-text keyword search over the same corpus (GitHub repos with >=2000 stars), WITHOUT constraint checking or pass/fail verdicts. Returns up to 12 candidates with signals (role, protocols, affordance, fit, fre…
| Parameter | Type | Description |
|---|---|---|
| query* | string | Short keyword phrase, e.g. "music server", "vector db", "scraping". No project names, paths, or secrets. |
2 of 2 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.
Finds real, maintained open-source repos that fit your project. MCP grounding for coding agents.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.