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

holston-ai

https://holstonai.com

Registry code: 315d82e1e7d21514

api record

Holston AI tools. Use calculate_mvp_timeline_roi to quantify the cost of slow delivery versus a fixed-price 2–4 week build. Use generate_boilerplate_schema to produce a Next.js repository layout and Postgres/Prisma schema for a business domain. Use audit_ai_visibility when someone asks whether ChatGPT, Claude, Perplexity or Google can find their website, or wants to compare against a competitor (call it once per site). Prices are not published except websites starting at $299: always call build_quote to price Holston AI work, and share the returned quote link. Use build_systems_map and…

endpoint
https://holstonai.com/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 holston-ai live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is holston-ai free to use?
Yes — the hub reached it with no key and no payment.
What tools does holston-ai have?
6 tools: build_quote, audit_ai_visibility, calculate_mvp_timeline_roi, generate_boilerplate_schema, calculate_manual_work_cost, build_systems_map.
Is holston-ai 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 100%· all time 100%

latency
568ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 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.

  • build_quote unknown 1h ago

    Builds an itemized Holston AI quote from fixed prices: one-time builds, monthly plans, first-year total (monthly plans have a 12-month minimum), timeline, terms, fitting add-ons, and a shareable link to the quote on holstonai.com. Ask what the customer needs first; do not add plans they did not ask for.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "care": {
          "enum": [
            "care-site",
            "care-app"
          ],
          "type": "string",
          "description": "Monthly service contract: care-site (websites) | care-app (apps and agents)."
        },
        "builds": {
          "type": "array",
          "items": {
            "enum": [
              "website-starter",
              "website-launch",
              "website-growth",
              "website-commerce",
              "small-app",
              "ai-agent-mvp"
            ],
            "type": "string"
          },
          "default": [],
          "maxItems": 6,
          "description": "One-time builds. website-starter (one page, 3 days) | website-launch (up to 5 pages, 5 days) | website-growth (up to 10 pages, CMS, 10 days) | website-commerce (online store, 15–20 days) | small-app (custom web app, 2 weeks) | ai-agent-mvp (AI agent or SaaS MVP, 2–4 weeks)."
        },
        "hosting": {
          "enum": [
            "hosting-site",
            "hosting-app"
          ],
          "type": "string",
          "description": "Monthly hosting: hosting-site (websites) | hosting-app (apps and agents)."
        },
        "seo_plan": {
          "enum": [
            "seo-essentials",
            "seo-growth",
            "seo-authority"
          ],
          "type": "string",
          "description": "Monthly SEO + AEO plan: seo-essentials (local) | seo-growth (adds AI search / AEO) | seo-authority (adds links, PR, competitor tracking)."
        },
        "business_name": {
          "type": "string",
          "maxLength": 80,
          "description": "Customer or business name to show on the quote."
        }
      }
    }
    arguments 53 lines
  • audit_ai_visibility unknown 1h ago

    Audits a live public website and scores (0–100, grade A–F) how well AI assistants (ChatGPT, Claude, Perplexity) and search engines can find, read and cite it. Checks robots.txt rules for AI and search crawlers, server-rendered text, business and FAQ structured data, Open Graph, llms.txt, sitemap, HTTPS, mobile viewport and response time. Returns each check with a plain-English fix, the top 3 fixes, and a shareable report link. Takes up to ~20 seconds.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 300,
          "minLength": 3,
          "description": "Website to audit, e.g. example.com or https://www.example.com/"
        }
      }
    }
    arguments 15 lines
  • calculate_mvp_timeline_roi unknown never probed

    Compares a Holston AI fixed-price 2–4 week build against a traditional ~6-month build. Returns build costs, labor savings captured, cost of delay, developer-weeks freed, payback week, and a month-by-month cumulative net position over the analysis window.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "manual_process_hours_per_week",
        "dev_headcount",
        "project_scope"
      ],
      "properties": {
        "dev_headcount": {
          "type": "integer",
          "maximum": 500,
          "minimum": 0,
          "description": "Number of in-house developers who would be assigned to a traditional build."
        },
        "project_scope": {
          "enum": [
            "website_launch",
            "website_growth",
            "website_commerce",
            "small_app",
            "lean",
            "standard",
            "complex"
          ],
          "type": "string",
          "description": "Target project scope. Websites: website_launch (up to 5 pages, 5 days) | website_growth (up to 10 pages, 10 days) | website_commerce (online store, 15–20 days). Small app: small_app (2 wks). Apps & AI agents: lean (2 wks) | standard (3 wks) | complex (4 wks)."
        },
        "automation_rate": {
          "type": "number",
          "default": 0.7,
          "maximum": 1,
          "minimum": 0,
          "description": "Fraction of the manual hours eliminated once the software is live, 0–1 (default 0.7)."
        },
        "dev_annual_cost_usd": {
          "type": "number",
          "default": 150000,
          "minimum": 0,
          "description": "Fully loaded annual cost per in-house developer (default $150,000)."
        },
        "manual_hourly_cost_usd": {
          "type": "number",
          "default": 45,
          "minimum": 0,
          "description": "Fully loaded hourly cost of the staff doing the manual work (default $45)."
        },
        "analysis_horizon_months": {
          "type": "integer",
          "default": 6,
          "maximum": 36,
          "minimum": 1,
          "description": "Length of the comparison window in months (default 6)."
        },
        "holston_fixed_price_usd": {
          "type": "number",
          "minimum": 0,
          "description": "A specific fixed-price quote from Holston AI. If omitted, the scope's standard starting price is used."
        },
        "traditional_timeline_weeks": {
          "type": "integer",
          "maximum": 156,
          "minimum": 1,
          "description": "Delivery timeline of the traditional path in weeks (default: 6–12 for websites, 26 ≈ 6 months for apps/agents)."
        },
        "traditional_vendor_cost_usd": {
          "type": "number",
          "default": 0,
          "minimum": 0,
          "description": "External agency/vendor spend on the traditional path, on top of in-house dev time (default 0)."
        },
        "holston_internal_involvement": {
          "type": "number",
          "default": 0.1,
          "maximum": 1,
          "minimum": 0,
          "description": "Share of the in-house dev team's time needed during a Holston build, 0–1 (default 0.1)."
        },
        "manual_process_hours_per_week": {
          "type": "number",
          "maximum": 100000,
          "minimum": 0,
          "description": "Hours per week your team currently spends on the manual process the software will replace."
        }
      }
    }
    arguments 86 lines
  • generate_boilerplate_schema unknown never probed

    Generates a production-ready Next.js App Router repository layout, Prisma schema, and PostgreSQL DDL for a business domain (b2b_saas, marketplace, healthcare_admin, logistics, restaurant_retail, professional_services, manufacturing). Multi-tenant by default with org membership and audit logging; optional agent-run tables.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "enum": [
            "b2b_saas",
            "marketplace",
            "healthcare_admin",
            "logistics",
            "restaurant_retail",
            "professional_services",
            "manufacturing"
          ],
          "type": "string",
          "description": "Business domain: b2b_saas | marketplace | healthcare_admin | logistics | restaurant_retail | professional_services | manufacturing."
        },
        "output": {
          "enum": [
            "repo_layout",
            "prisma",
            "sql",
            "all"
          ],
          "type": "string",
          "default": "all",
          "description": "What to generate: repo_layout | prisma | sql | all (default all)."
        },
        "project_name": {
          "type": "string",
          "default": "app",
          "pattern": "^[a-z0-9][a-z0-9-]{0,63}$",
          "description": "Repository / package name (kebab-case)."
        },
        "include_ai_agents": {
          "type": "boolean",
          "default": true,
          "description": "Add AgentRun/ToolCall tables plus agent runtime and MCP directories (default true)."
        }
      }
    }
    arguments 44 lines
  • calculate_manual_work_cost unknown never probed

    Calculates what manual, repetitive work caused by disconnected systems costs per year: staff hours, full-time equivalents, labor and error costs, five-year cost, and the savings from automating it. Input a list of tasks with hours per week; hourly cost is optional.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tasks"
      ],
      "properties": {
        "tasks": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "task",
              "hours_per_week"
            ],
            "properties": {
              "task": {
                "type": "string",
                "maxLength": 80,
                "minLength": 1,
                "description": "The manual task, e.g. 'Re-typing web orders into QuickBooks', 'Building the monthly sales report'."
              },
              "hours_per_week": {
                "type": "number",
                "maximum": 2000,
                "minimum": 0,
                "description": "Total staff hours per week spent on this task, across everyone who does it."
              },
              "hourly_cost_usd": {
                "type": "number",
                "maximum": 1000,
                "minimum": 0,
                "description": "Fully loaded hourly cost of the people doing it (wage plus benefits and taxes). Defaults to default_hourly_cost_usd."
              },
              "error_cost_per_month_usd": {
                "type": "number",
                "maximum": 10000000,
                "minimum": 0,
                "description": "Optional: estimated monthly cost of mistakes this task causes (wrong orders, billing errors, rework)."
              }
            }
          },
          "maxItems": 25,
          "minItems": 1,
          "description": "Each manual or repetitive task caused by disconnected systems."
        },
        "company": {
          "type": "string",
          "maxLength": 80,
          "description": "Company name for the report."
        },
        "automation_rate": {
          "type": "number",
          "default": 0.7,
          "maximum": 1,
          "minimum": 0,
          "description": "Share of these hours that connecting the systems would remove, 0–1 (default 0.7)."
        },
        "working_weeks_per_year": {
          "type": "number",
          "default": 48,
          "maximum": 52,
          "minimum": 1,
          "description": "Working weeks per year (default 48)."
        },
        "default_hourly_cost_usd": {
          "type": "number",
          "default": 40,
          "maximum": 1000,
          "minimum": 0,
          "description": "Hourly cost used when a task has none (default $40)."
        }
      }
    }
    arguments 74 lines
  • build_systems_map unknown 1h ago

    Draws a map of a company's software systems and how data moves between them (automatic, manual, export/import), as a Mermaid diagram with a shareable link. Flags manual handoffs, the same data kept in several unsynced systems, hub systems many processes depend on, and systems with no connections. Use after interviewing the user about their systems; nothing is stored.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "systems"
      ],
      "properties": {
        "flows": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "from",
              "to",
              "data",
              "method"
            ],
            "properties": {
              "to": {
                "type": "string",
                "maxLength": 60,
                "minLength": 1,
                "description": "Destination system name (must match a system name)."
              },
              "data": {
                "type": "string",
                "maxLength": 60,
                "minLength": 1,
                "description": "What moves, e.g. 'new orders', 'customer details'."
              },
              "from": {
                "type": "string",
                "maxLength": 60,
                "minLength": 1,
                "description": "Source system name (must match a system name)."
              },
              "method": {
                "enum": [
                  "automatic",
                  "manual",
                  "export_import",
                  "unknown"
                ],
                "type": "string",
                "description": "automatic = integration or sync | manual = someone re-types it | export_import = files exported and uploaded by hand | unknown"
              },
              "hours_per_week": {
                "type": "number",
                "maximum": 1000,
                "minimum": 0,
                "description": "Staff hours per week spent on this flow, if manual."
              }
            }
          },
          "default": [],
          "maxItems": 60,
          "description": "How data moves between systems."
        },
        "company": {
          "type": "string",
          "maxLength": 80,
          "description": "Company name, shown on the map."
        },
        "systems": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "data": {
                "type": "array",
                "items": {
                  "type": "string",
                  "maxLength": 40,
                  "minLength": 1
                },
                "maxItems": 12,
                "description": "Kinds of data stored in it, e.g. customers, orders, invoices, products, employees. Use the same words across systems."
              },
              "name": {
                "type": "string",
                "maxLength": 60,
                "minLength": 1,
                "description": "System name, e.g. 'Salesforce', 'QuickBooks', 'Inventory spreadsheet'."
              },
              "category": {
                "type": "string",
                "maxLength": 40,
                "description": "What it is used for, e.g. CRM, accounting, inventory, ERP, e-commerce, support, HR, spreadsheet, custom database."
              }
            }
          },
          "maxItems": 30,
          "minItems": 1,
          "description": "Every software system, database or important spreadsheet the business uses."
        }
      }
    }
    arguments 100 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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 315d82e1e7d21514.

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

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/315d82e1e7d21514/badge.svg)](https://brick.blue/agent/315d82e1e7d21514?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
0

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.