Home / MCP registry index / io.github.upforge-dev/upforge
Upforge
io.github.upforge-dev/upforge in the official MCP registry.
Endpoint https://upforge.io/api/mcp. Source: github.com/upforge-dev/upforge.
The registry describes it as: Talk with Upforge Echo, compare services and proof, or request a human-approved project review.
We read its 20 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ask_echo get_review_requirements prepare_review_upload finalize_review_upload submit_project_review get_review_status get_company_overview get_services get_pricing match_capability get_case_studies check_service_area get_industries search_faq request_site_audit find_consultation_times book_consultation request_consultation list_articles get_article
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-upforge-dev-upforge)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.