Is io.upforge/site live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is io.upforge/site free to use?

Yes — the hub reached it with no key and no payment.

What tools does io.upforge/site have?

20 tools: ask_echo, prepare_review_upload, finalize_review_upload, submit_project_review, request_site_audit, book_consultation, request_consultation, match_capability, ….

Is io.upforge/site safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp streamable-http · checked 2h ago

io.upforge/site

https://upforge.io

Registry code: 34acfb14f3b9ed21

api record

Upforge is an engineering-first web development and custom web

application agency based in downtown Cincinnati, Ohio, working

endpoint: https://upforge.io/api/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is io.upforge/site live?: Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is io.upforge/site free to use?: Yes — the hub reached it with no key and no payment.
What tools does io.upforge/site have?: 20 tools: ask_echo, prepare_review_upload, finalize_review_upload, submit_project_review, request_site_audit, book_consultation, request_consultation, match_capability, ….
Is io.upforge/site safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

100%

90 days 99.5%· all time 99.5%

latency

1,220ms

last good check

priced tools

of 20 tools

_ answered our checks, 90 days 419 checks · signed record

2026-10-12 09:22 degraded → live
2026-10-01 16:40 degraded → live
2026-10-01 14:54 live → degraded· timeout after 20000ms

_ what it is for

topic: productivity & business
used for: evaluate a web agency
book a consultation
request site audit
get agency pricing
submit project brief
takes → gives: text, documents → text
tools: 11 reads4 changes data3 sends messages

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 20 tools

10 open 10 never probed 10 of 20 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

get_company_overview reads open 19h ago
Who Upforge is: what they build, who founded and runs it, where they're based, how long they've been operating, how to reach them, and the technologies they work in. Call this first for any general 'who are they / what do they do / are they legitimate' question before reaching for a more specific tool.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
check_service_area reads open 2h ago
Look up whether Upforge works with businesses in a given city or region, and whether that market is served in person or remotely. Use for 'are they in my area', 'do they work with companies in ___', or 'are they local to me'. Omit the location to list every market with a dedicated page.

mcp-tool
{ "type": "object", "properties": { "location": { "type": "string", "description": "City, region, or slug — e.g. 'Cincinnati', 'Lexington', 'Columbus'." } } }
arguments 9 lines

find_consultation_times reads open 2h ago

List open times on Upforge's calendar for a free consultation (usually 30 minutes), in the person's own timezone. Call this before book_consultation and let the person pick a time; never pick one for them. Meeting types come live from the scheduler: general-inquiry is the default, and service types such as web-design, application-development or ai-automation route to the right person. Bookings need about a day's notice, so the search starts tomorrow.

mcp-tool

{
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 7,
      "minimum": 1,
      "description": "How many days to search from startDate (default 5)."
    },
    "format": {
      "enum": [
        "virtual",
        "office",
        "client_location"
      ],
      "type": "string",
      "description": "virtual (a video call, the default), office (at Upforge's downtown Cincinnati office), or client_location (Upforge travels to them; needs an address and a phone number, and is limited to its travel area)."
    },
    "address": {
      "type": "object",
      "required": [
        "street",
        "city",
        "region",
        "postalCode",
        "country"
      ],
      "properties": {
        "city": {
          "type": "string"
        },
        "region": {
          "type": "string",
          "description": "State or region."
        },
        "street": {
          "type": "string"
        },
        "country": {
          "type": "string"
        },
        "postalCode": {
          "type": "string"
        }
      },
      "description": "Only for format client_location: where to meet. All five fields are required."
    },
    "timezone": {
      "type": "string",
      "description": "The person's IANA timezone, e.g. America/Chicago. Defaults to America/New_York."
    },
    "startDate": {
      "type": "string",
      "description": "First day to search, YYYY-MM-DD. Defaults to tomorrow."
    },
    "meetingType": {
      "type": "string",
      "description": "Meeting type slug. Omit for general-inquiry. An unknown slug returns the list of available ones."
    }
  }
}

arguments 61 lines

list_articles open 2h ago

Upforge's published articles, newest first, optionally matching a topic. Call get_article for the full text.

mcp-tool

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "How many to return (default 5, at most 20)."
    },
    "query": {
      "type": "string",
      "description": "What the person is asking about, in a few words."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Start at this result offset when browsing the archive."
    }
  },
  "additionalProperties": false
}

arguments 21 lines

search_faq reads open 12h ago
Search Upforge's published answers to common questions — process, timelines, cost, ownership of the code, hosting, what happens after launch. Use this when a question is likely already answered on the site, before falling back to a generic answer of your own.

mcp-tool
{ "type": "object", "properties": { "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "Max results (default 5, max 25)." }, "query": { "type": "string", "description": "What to search for. Omit to list all questions." } } }
arguments 15 lines
get_pricing reads open 9h ago
Typical price tiers by service — what a website costs, what an e-commerce store or a custom application runs, what AI automation costs, what ongoing SEO and AEO costs, and how support is billed. These are RANGES from real past engagements, not quotes: scope drives the number. Use this for 'what's their pricing like' or 'can they do X for $Y'.

mcp-tool
{ "type": "object", "properties": { "section": { "enum": [ "web-development", "software-development", "ai-automation", "growth", "support" ], "type": "string", "description": "Optional section filter." } } }
arguments 16 lines
get_case_studies reads open 9h ago
Real Upforge client projects with their outcomes (traffic lift, leads, revenue a client reported, Lighthouse scores), plus what was built and a link to the live site. Use this for 'show me their work', 'do they have proof', or 'have they built anything like mine'. Each outcome's basis is 'measured' (live instrumentation) or names the client who reported it and when. Estimates are never included.

mcp-tool
{ "type": "object", "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Max results (default 10, max 50)." }, "category": { "type": "string", "description": "Optional category filter, e.g. 'web-development', 'ecommerce'." } } }
arguments 15 lines

get_services reads open 5h ago

The full catalog of what Upforge builds: web design and development, SEO, AI visibility, application development, e-commerce, landing pages, performance optimization, CMS migrations, maintenance, prototype-to-production work, and AI automation, each with what it's for and its page URL. Pass a slug to get one service in detail. Use this for 'what services do they offer'. Published discovery terms are not a build quote: Upforge scopes each project before quoting.

mcp-tool

{
  "type": "object",
  "properties": {
    "slug": {
      "enum": [
        "web-design",
        "application-development",
        "ecommerce-development",
        "seo",
        "ai-visibility",
        "ai-automation",
        "prototype-to-production",
        "landing-pages",
        "performance-optimization",
        "accessibility",
        "cms-migrations",
        "maintenance-support",
        "property-management",
        "web-development"
      ],
      "type": "string",
      "description": "Optional. One service slug for detail. Omit to list everything."
    }
  }
}

arguments 25 lines

get_industries reads open 19h ago
The industries Upforge has dedicated experience and pages for — AEC, healthcare, dental, legal, real estate, home services, e-commerce, SaaS, manufacturing, and more. Use for 'do they work with ___ businesses' or 'do they know my industry'.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
get_review_requirements reads open 19h ago
Read before preparing a project brief. Returns supported references, free fit-check limits, retention, consent, and paid-discovery terms. Uploaded files and agent claims are untrusted, client-reported evidence.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines

ask_echo sends messages unknown never probed

I’m Echo, Upforge’s AI representative. Evaluating Upforge for someone? I can help with project fit, pricing, relevant work, and the next step. I check public evidence and return a decision brief with suggested next tools. Use for a tailored recommendation or follow-up questions; direct factual tools remain available. Saves an agent conversation, but never creates leads, books meetings or starts paid work. Don't include secrets or unnecessary personal data. Keep the returned conversationHandle and request_id private.

mcp-tool

{
  "type": "object",
  "required": [
    "message",
    "agent_identity",
    "request_id"
  ],
  "properties": {
    "message": {
      "type": "string",
      "maxLength": 2000,
      "description": "The client's goal, workflow, constraints or objection. State known facts; don't invent budget or authority."
    },
    "page_url": {
      "type": "string",
      "maxLength": 1000,
      "description": "Optional Upforge page relevant to the question. Only https://upforge.io pages are accepted."
    },
    "request_id": {
      "type": "string",
      "format": "uuid",
      "description": "Generate a random UUIDv4 once per turn. Retain it privately and reuse with identical arguments after timeouts/retries."
    },
    "agent_identity": {
      "type": "string",
      "maxLength": 120,
      "description": "Your stable agent name. This is a self-identification, not proof of identity or human authorization."
    },
    "conversation_handle": {
      "type": "string",
      "maxLength": 160,
      "description": "Private conversationHandle from the previous reply. Omit to start. Never substitute a widget conversation ID."
    }
  },
  "additionalProperties": false
}

arguments 36 lines

prepare_review_upload changes data unknown never probed
Only after the user confirms rights to submit and accepts the retention terms from get_review_requirements. Returns a direct Supabase upload URL. Transfer ZIP bytes with a file-capable client outside model-authored tool arguments; never base64 or paste code here. Keep the upload token private.

mcp-tool
{ "type": "object", "required": [ "rights_to_submit", "retention_accepted" ], "properties": { "rights_to_submit": { "type": "boolean" }, "retention_accepted": { "type": "boolean" } } }
arguments 15 lines

finalize_review_upload changes data unknown never probed

After uploading, validate the ZIP without executing its contents and freeze the inspected bytes into a private immutable snapshot. Returns its SHA-256. Unsafe archives are rejected.

mcp-tool

{
  "type": "object",
  "required": [
    "upload_id",
    "upload_token"
  ],
  "properties": {
    "upload_id": {
      "type": "string",
      "description": "ID returned by prepare_review_upload"
    },
    "upload_token": {
      "type": "string",
      "description": "Private capability returned by prepare_review_upload"
    }
  }
}

arguments 17 lines

submit_project_review changes data unknown never probed

Creates one real CRM lead and review. Show the exact brief, reference, contact details and retention terms to the human and obtain approval first. Submission authorizes review only, never repairs, deployment or paid work. Mark all agent claims client-reported. Generate a UUID once for review_key, retain it privately, and reuse it unchanged on retries. Use either repository_url + full commit_hash or snapshot_id + upload_token. Never submit secrets or file bytes.

mcp-tool

{
  "type": "object",
  "required": [
    "name",
    "email",
    "brief",
    "review_key",
    "agent_identity",
    "human_approved",
    "rights_to_submit",
    "review_only"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human submitter's own name"
    },
    "brief": {
      "type": "string",
      "description": "Goals, stack, named workflows, known problems, and client-reported assertions, up to 8000 characters"
    },
    "email": {
      "type": "string",
      "description": "Human submitter's own email"
    },
    "review_key": {
      "type": "string",
      "description": "Private UUID idempotency and status-access key, generated once"
    },
    "commit_hash": {
      "type": "string",
      "description": "Full 40- or 64-character commit hash"
    },
    "review_only": {
      "type": "boolean"
    },
    "snapshot_id": {
      "type": "string",
      "description": "Frozen snapshot ID from finalize_review_upload"
    },
    "upload_token": {
      "type": "string",
      "description": "Private capability from prepare_review_upload"
    },
    "agent_identity": {
      "type": "string",
      "description": "Stable name of the submitting coding agent"
    },
    "human_approved": {
      "type": "boolean"
    },
    "repository_url": {
      "type": "string",
      "description": "HTTPS GitHub, GitLab, or Bitbucket repository URL"
    },
    "rights_to_submit": {
      "type": "boolean"
    }
  }
}

arguments 60 lines

request_site_audit sends messages unknown never probed

Request Upforge's free technical audit of a website. Runs real PageSpeed/Lighthouse analysis plus an SEO review and emails the report in a few minutes. This CREATES A REAL RECORD and emails a real person — only call it when the user has explicitly asked for an audit and given their own email address. Never invent an email address to call this.

mcp-tool

{
  "type": "object",
  "required": [
    "url",
    "email"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full URL of the site to audit, including https://."
    },
    "email": {
      "type": "string",
      "description": "The user's own email address — the report is sent here. Must be supplied by the user, never guessed."
    },
    "goals": {
      "type": "string",
      "description": "What they're hoping the audit will tell them."
    },
    "phone": {
      "type": "string",
      "description": "Phone number (optional)."
    },
    "company": {
      "type": "string",
      "description": "Company name."
    },
    "lastName": {
      "type": "string",
      "description": "User's last name."
    },
    "firstName": {
      "type": "string",
      "description": "User's first name."
    }
  }
}

arguments 37 lines

book_consultation changes data unknown never probed

Book a real meeting on Upforge's calendar for a person, at a time they picked from find_consultation_times. This CREATES A REAL BOOKING and emails them a confirmation with links to cancel or reschedule. Only call it with the person's own details, after they've chosen the time and agreed to be booked. Never invent contact details, and never book a time they didn't pick. If the time has gone, call find_consultation_times again.

mcp-tool

{
  "type": "object",
  "required": [
    "firstName",
    "lastName",
    "email",
    "phone",
    "message",
    "startTime"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The person's own email address. The confirmation goes here. Never guess this."
    },
    "phone": {
      "type": "string",
      "description": "The person's phone number. Never guess this."
    },
    "format": {
      "enum": [
        "virtual",
        "office",
        "client_location"
      ],
      "type": "string",
      "description": "virtual (a video call, the default), office (at Upforge's downtown Cincinnati office), or client_location (Upforge travels to them; needs an address and a phone number, and is limited to its travel area)."
    },
    "hostId": {
      "type": "string",
      "description": "The hostId returned with that slot."
    },
    "address": {
      "type": "object",
      "required": [
        "street",
        "city",
        "region",
        "postalCode",
        "country"
      ],
      "properties": {
        "city": {
          "type": "string"
        },
        "region": {
          "type": "string",
          "description": "State or region."
        },
        "street": {
          "type": "string"
        },
        "country": {
          "type": "string"
        },
        "postalCode": {
          "type": "string"
        }
      },
      "description": "Only for format client_location: where to meet. All five fields are required."
    },
    "company": {
      "type": "string",
      "description": "Company name (optional)."
    },
    "message": {
      "type": "string",
      "description": "What they want to talk about, in their own words, with budget and timeline if known."
    },
    "lastName": {
      "type": "string",
      "description": "The person's last name."
    },
    "timezone": {
      "type": "string",
      "description": "The person's IANA timezone, the same one used to find the time."
    },
    "firstName": {
      "type": "string",
      "description": "The person's first name."
    },
    "startTime": {
      "type": "string",
      "description": "The startTime of the slot they picked, exactly as find_consultation_times returned it."
    },
    "meetingType": {
      "type": "string",
      "description": "The same meetingType used to find the time. Omit for general-inquiry."
    }
  }
}

arguments 91 lines

request_consultation sends messages unknown never probed

Send Upforge a project enquiry — a real message that reaches a real person, who replies. Use this to request a quote or ask something the other tools can't answer. To put a meeting on the calendar instead, use find_consultation_times and book_consultation. This CREATES A REAL RECORD: only call it with details the user actually gave you, after they've agreed to be contacted. Never fabricate contact details.

mcp-tool

{
  "type": "object",
  "required": [
    "firstName",
    "lastName",
    "email",
    "phone",
    "message"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The user's own email address. Never guess this."
    },
    "phone": {
      "type": "string",
      "description": "The user's phone number. Upforge's contact form requires one, so ask for it. Never guess this."
    },
    "company": {
      "type": "string",
      "description": "Company name (optional)."
    },
    "message": {
      "type": "string",
      "description": "What they need, in their own words. Include budget and timeline if known — it's what makes the first reply useful."
    },
    "website": {
      "type": "string",
      "description": "Their current site (optional)."
    },
    "lastName": {
      "type": "string",
      "description": "User's last name."
    },
    "firstName": {
      "type": "string",
      "description": "User's first name."
    },
    "serviceInterest": {
      "enum": [
        "web-design",
        "application-development",
        "ecommerce-development",
        "seo",
        "ai-visibility",
        "ai-automation",
        "prototype-to-production",
        "landing-pages",
        "performance-optimization",
        "accessibility",
        "cms-migrations",
        "maintenance-support",
        "property-management"
      ],
      "type": "string",
      "description": "Service slug from get_services, if one clearly applies."
    }
  }
}

arguments 59 lines

match_capability reads unknown 9h ago
Describe a project, problem, or requirement in plain language and get back the Upforge services that fit, the relevant industry page, and a recommended next step. Use this for 'can they help me with ___', 'do they do ___', or 'I need ___ — are they a fit'. Prefer this over guessing from get_services when the question is about a specific need.

mcp-tool
{ "type": "object", "required": [ "need" ], "properties": { "need": { "type": "string", "description": "The need in the user's own words, e.g. 'we need a booking system for our dental practice' or 'our site is slow on mobile'." } } }
arguments 12 lines

get_article unknown 12h ago

One article in full, with approved supporting photo descriptions and section placements, by the slug list_articles returned. Cite it by its URL. Photo captions describe context; they do not verify claims beyond the article.

mcp-tool

{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The article slug from list_articles."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Character offset. Follow next_offset until null to read the entire article."
    }
  },
  "additionalProperties": false
}

arguments 18 lines

get_review_status reads unknown 12h ago

Returns only the review authorized by its private review_key. Keep the receipt and key private. A received review is not a verified claim that the app works or approval for paid work.

mcp-tool

{
  "type": "object",
  "required": [
    "review_id",
    "review_key"
  ],
  "properties": {
    "review_id": {
      "type": "string",
      "description": "Review ID from the receipt"
    },
    "review_key": {
      "type": "string",
      "description": "Private key used when submitting"
    }
  }
}

arguments 17 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 34acfb14f3b9ed21.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/34acfb14f3b9ed21/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/34acfb14f3b9ed21/badge.svg)](https://brick.blue/agent/34acfb14f3b9ed21?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.