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

Is Total CMS free to use?

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

What tools does Total CMS have?

20 tools: fetch, find_comparison, list_guides, describe_collection, describe_view, docs_get, docs_lookup, docs_search, ….

Is Total CMS 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 1h ago

Total CMS

https://totalcms.co

Registry code: 825742ba0c10ae59

api record

Total CMS site exposed over the Model Context Protocol. Content is collections of objects shaped by schemas, stored as files; there is no database. Vocabulary: collection (not table), object (not row), schema (not model), Site Builder page (not template). Discover before you act: list_collections returns every collection with its filterable fields; describe_collection and get_schema give the shape and each property's help text. Read with query_collection, get_object and search_collection, or the resources tcms://{collection}/ and tcms://{collection}/{id}. Drafts are hidden from anonymous…

endpoint: https://totalcms.co/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 Total CMS live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Total CMS free to use?: Yes — the hub reached it with no key and no payment.
What tools does Total CMS have?: 20 tools: fetch, find_comparison, list_guides, describe_collection, describe_view, docs_get, docs_lookup, docs_search, ….
Is Total CMS 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

438ms

last good check

priced tools

of 20 tools

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

2026-10-24 05:36 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

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 20 tools

3 open 17 never probed 3 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.

latest_release open 1h ago
The most recent Total CMS release: version, title, date and the release summary. Returns: paginated releases objects with url per item.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
list_collections open 1h ago
Discover the collections visible to you. Lean overview — one entry per collection. Returns id, name (display label), schema (the schema id this collection uses), description, url_pattern, access level, and total_objects (so you can decide whether to paginate or enumerate). For the per-property detail of one collection (which properties exist, which are filterable/sortable), call describe_collection. Then query_collection / search_collection / get_object for the data.

mcp-tool
{ "type": "object", "properties": {}, "additionalProperties": false }
arguments 5 lines
list_views open 1h ago
Discover the pre-computed data views visible to you. Lean overview — one entry per view. Data views are Twig-defined queries that aggregate across collections; their result is cached and accessible by id. Returns id, name, description, last_built, and access. Use the id with query_view (paginated query), get_view (fetch the whole cached result), or describe_view (output shape + metadata). For raw collection content use list_collections instead.

mcp-tool
{ "type": "object", "properties": {}, "additionalProperties": false }
arguments 5 lines
fetch unknown never probed
Fetch the full document for a search result id. Returns {id, title, text, url, metadata}; `text` is the readable body for citation. Pass an id returned by the `search` tool.

mcp-tool
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "A document id returned by the `search` tool." } }, "additionalProperties": false }
arguments 13 lines
find_comparison unknown never probed
Find the head-to-head comparison page for a competitor by name (case-insensitive partial match). Returns the full page content including the feature table. Parameters: - competitor (string, required): Competitor name, e.g. "Kirby" or "Craft". Returns: paginated comparisons objects with url per item.

mcp-tool
{ "type": "object", "required": [ "competitor" ], "properties": { "competitor": { "type": "string", "description": "Competitor name, e.g. \"Kirby\" or \"Craft\"." } } }
arguments 12 lines
list_guides unknown never probed
The site's Guides: evergreen buying-guide pages served at /guides/{id}, stored in the roundups collection. Returns every guide in display order with its id, heading, lede, reviewed date and draft flag. A guide's full content (contenders, choose, howToChoose, faqs, sources) is on the object itself: get_object with collection "roundups". Returns: paginated roundups objects with url per item.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
describe_collection unknown never probed
Describe one collection in detail. Returns the collection metadata plus a properties array — each entry is a property with its type, description, and indexed/filterable/sortable flags. Call list_collections first to find a collection id, then describe_collection to see what is queryable inside it. `indexed: true` means the property appears in query_collection / search_collection results (and may be filterable/sortable). `indexed: false` means the property exists on objects but is not returned by query/search — retrieve it through get_object instead.

mcp-tool
{ "type": "object", "required": [ "collection" ], "properties": { "collection": { "type": "string", "examples": [ "blog", "products", "team" ], "description": "Collection id (slug-form). Use list_collections to discover available collections." } }, "additionalProperties": false }
arguments 18 lines
describe_view unknown never probed
Describe one data view in detail. Returns metadata (id, name, description, last_built, access, total_items) plus output_shape — the list of keys present on the first cached item, sampled so agents can compose effective query_view / get_view calls. Admin callers also receive the view's Twig definition for dev visibility. Use list_views to discover view ids first.

mcp-tool
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "examples": [ "recent-posts", "monthly-sales-summary" ], "description": "View id. Use list_views to discover available views." } }, "additionalProperties": false }
arguments 17 lines
docs_get unknown never probed
Fetch a full Total CMS documentation page as markdown by its path (as returned by docs_search), e.g. "twig/data" or "site-builder/overview".

mcp-tool
{ "type": "object", "required": [ "path" ], "properties": { "path": { "type": "string", "description": "Documentation page path from docs_search results" } } }
arguments 12 lines

docs_lookup unknown never probed

Look up a specific Total CMS reference entry: Twig functions/filters, field types, REST API endpoints, schema configuration keys, CLI commands, extension API, or builder API. Omit `name` to list all entries of a kind.

mcp-tool

{
  "type": "object",
  "required": [
    "kind"
  ],
  "properties": {
    "kind": {
      "enum": [
        "twig_function",
        "twig_filter",
        "field_type",
        "api_endpoint",
        "schema_config",
        "cli_command",
        "extension_api",
        "builder_api"
      ],
      "type": "string"
    },
    "name": {
      "type": "string",
      "description": "Entry name (function name, field type, \"GET /api/collections\", command name…). Omit to list the kind."
    }
  }
}

arguments 25 lines

docs_search unknown never probed

Search the Total CMS documentation. Returns matching pages with their path, title, group, and section headings. Use docs_get with a returned path to read the full page.

mcp-tool

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Maximum results (default 8, max 20)"
    },
    "query": {
      "type": "string",
      "description": "Search terms, e.g. \"image resize twig\" or \"webhook automation\""
    }
  }
}

arguments 16 lines

get_object unknown never probed
Fetch a single object by its id from a collection. Returns the full object as a flat map of fields, decorated with a `url` field where the collection has a public URL pattern configured. This tool does not search or filter — use query_collection for paginated lists or search_collection for free-text search. Available collections and filterable properties: - articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable) - comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - roundups — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)

mcp-tool
{ "type": "object", "required": [ "collection", "id" ], "properties": { "id": { "type": "string", "examples": [ "hello-world", "fall-collection-2025" ], "description": "Object id (slug). Get candidate ids from query_collection or search_collection output." }, "format": { "enum": [ "markdown", "html", "text" ], "type": "string", "default": "markdown", "description": "Rendered format for content fields. Accepted now for forward-compat; full conversion ships with the Tiptap→markdown converter in a later release." }, "locale": { "type": "string", "default": "", "description": "BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today." }, "collection": { "type": "string", "examples": [ "blog", "products" ], "description": "Collection id. Use list_collections to discover available collections." } }, "additionalProperties": false }
arguments 41 lines
get_resource unknown never probed
Resolve a tcms:// resource URI to its underlying object. Format: tcms://{collection}/{id} — e.g. tcms://blog/hello-world. Equivalent to calling get_object with the parsed collection and id; returns the same shape. Use this when a URI has been surfaced to you (in other tool output, in user input, etc.); use get_object directly when you have a separate collection + id pair. Extension-registered URIs (other schemes) are reachable via the resources/read transport surface.

mcp-tool
{ "type": "object", "required": [ "uri" ], "properties": { "uri": { "type": "string", "examples": [ "tcms://blog/hello-world", "tcms://products/fall-collection-2025" ], "description": "A tcms:// resource URI identifying one object. Format: tcms://{collection}/{id}." } }, "additionalProperties": false }
arguments 17 lines

get_view unknown never probed

Fetch a data view's full cached result by id. Output is freeform — each item's field set depends on the view's Twig definition. Call describe_view first to learn the expected shape. Capped at 50 items; larger views return the first 50 plus a hint to call query_view for pagination. For per-item paginated access use query_view directly.

mcp-tool

{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "examples": [
        "recent-posts",
        "monthly-sales-summary"
      ],
      "description": "View id. Use list_views to discover available views."
    },
    "format": {
      "enum": [
        "markdown",
        "html",
        "text"
      ],
      "type": "string",
      "default": "markdown",
      "description": "Forward-compat with collection tools. View data is freeform so this has no effect today."
    },
    "locale": {
      "type": "string",
      "default": "",
      "description": "BCP 47 locale tag — forward-compat for the 3.6 i18n release. No effect today."
    }
  },
  "additionalProperties": false
}

arguments 32 lines

needs_review unknown never probed
Comparison pages ordered by how long ago their competitor facts were last verified, oldest first. Pass `before` (ISO date) to return only pages last verified before that date. Each page shows its verification date publicly, so keeping these fresh matters. Parameters: - before (string, optional): Only pages whose reviewed date is on or before this ISO date (optional). Returns: paginated comparisons objects with url per item.

mcp-tool
{ "type": "object", "properties": { "before": { "type": "string", "format": "date", "description": "Only pages whose reviewed date is on or before this ISO date (optional)." } } }
arguments 10 lines
query_collection unknown never probed
Query a collection for paginated content. Returns the matching items plus pagination metadata (total, limit, offset, has_more); each item is decorated with a public `url` field where one is configured. Use REST-style `include` / `exclude` filter strings (comma-separated field:value pairs; AND-semantics for include, OR-semantics for exclude) and `sort` (e.g. `date:desc`). Only properties listed in the catalog below are queryable — other schema properties exist on objects but are not filterable here; use get_object if you need the full record or describe_collection to see every property. This tool does not free-text search content — use search_collection for that. It does not fetch a single object by id — use get_object. Available collections and filterable properties: - articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable) - comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - roundups — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)

mcp-tool
{ "type": "object", "required": [ "collection" ], "properties": { "sort": { "type": "string", "default": "", "examples": [ "date:desc", "title:asc" ], "description": "Sort rule \"field:direction\"; multiple rules comma-separated. Only fields marked sortable in the catalog will sort." }, "limit": { "type": "integer", "default": 10, "maximum": 50, "minimum": 1, "description": "Maximum items to return. Capped at 50 (vs. REST's 100) to fit MCP response-size budgets." }, "format": { "enum": [ "markdown", "html", "text" ], "type": "string", "default": "markdown", "description": "Rendered format for content fields. Accepted now for forward-compat; full conversion ships with the Tiptap→markdown converter in a later release." }, "locale": { "type": "string", "default": "", "description": "BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today." }, "offset": { "type": "integer", "default": 0, "minimum": 0, "description": "Number of items to skip — combine with limit for pagination." }, "exclude": { "type": "string", "default": "", "examples": [ "draft:true", "status:archived,featured:false" ], "description": "Comma-separated field:value pairs that exclude items (OR). Drafts the caller may not see are removed before this filter runs, whatever it says." }, "include": { "type": "string", "default": "", "examples": [ "featured:true", "category:tech,published:true" ], "description": "Comma-separated field:value pairs items must ALL match. Wildcards \"*foo*\", \"foo*\", \"*foo\" supported." }, "collection": { "type": "string", "examples": [ "blog", "products", "team" ], "description": "Collection id (slug-form). Use list_collections to discover available collections." } }, "additionalProperties": false }
arguments 73 lines

query_view unknown never probed

Paginated query against a data view's cached result. REST-syntax include/exclude/sort, same vocabulary as query_collection. View data is freeform — call describe_view first to learn the field set before composing filters. `limit` is capped at 50; use offset to paginate larger views.

mcp-tool

{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "examples": [
        "recent-posts",
        "monthly-sales-summary"
      ],
      "description": "View id from list_views."
    },
    "sort": {
      "type": "string",
      "description": "Sort spec, e.g. \"date:desc\"."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1
    },
    "format": {
      "enum": [
        "markdown",
        "html",
        "text"
      ],
      "type": "string",
      "default": "markdown",
      "description": "Forward-compat with query_collection; no effect today since view data is freeform."
    },
    "locale": {
      "type": "string",
      "default": "",
      "description": "Forward-compat for 3.6 i18n."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0
    },
    "exclude": {
      "type": "string",
      "examples": [
        "draft:true"
      ],
      "description": "REST-style negative filter."
    },
    "include": {
      "type": "string",
      "examples": [
        "featured:true",
        "year:2025"
      ],
      "description": "REST-style filter, e.g. \"category:tech,published:true\". Field names depend on the view's output shape."
    }
  },
  "additionalProperties": false
}

arguments 62 lines

search unknown never probed
Search site content across all collections you can see. Returns matching results as {id, title, url}; pass a result id to `fetch` to read the full document. Drafts are hidden from anonymous callers.

mcp-tool
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Search terms." } }, "additionalProperties": false }
arguments 13 lines
search_collection unknown never probed
Free-text search within a single collection. Returns matching items decorated with a public `url`; total reflects what was found. Supports AND (default), OR, and "quoted phrases". Searches across the properties listed in the catalog below — other schema properties exist on objects but are not searchable here; use get_object for the full record or describe_collection to see every property. This tool does not filter by field value — use query_collection with `include`/`exclude` for that. Drafts are auto-hidden from anonymous callers. Available collections and filterable properties: - articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable) - comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - roundups — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)

mcp-tool
{ "type": "object", "required": [ "collection", "query" ], "properties": { "limit": { "type": "integer", "default": 10, "maximum": 50, "minimum": 1, "description": "Maximum items to return (capped at 50 to fit MCP response-size budgets)." }, "query": { "type": "string", "examples": [ "rust performance", "\"static analysis\"", "php or python" ], "description": "Search terms. AND-semantics by default; use `or` between terms for OR; wrap phrases in double quotes." }, "format": { "enum": [ "markdown", "html", "text" ], "type": "string", "default": "markdown", "description": "Output format for styledtext properties on the matched items. markdown is friendliest for AI consumption." }, "locale": { "type": "string", "default": "", "description": "BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today." }, "collection": { "type": "string", "examples": [ "blog", "products" ], "description": "Collection id to search within. Use list_collections to discover available collections." } }, "additionalProperties": false }
arguments 49 lines

search_collections unknown never probed

Full-text search across every collection you can see, in one call. Returns matching items each decorated with `collection` (which collection the hit came from) and `url`. Pair `collection` + `id` to fetch the full record via get_object. Call list_collections for the available collections and describe_collection on any one for its full property list; properties not flagged filterable there exist on objects but are not searched here (use get_object for the full record). For a single-collection search use search_collection instead — same query syntax, scoped tighter. Drafts are auto-hidden from anonymous callers.

mcp-tool

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum items returned in aggregate across all collections. Capped at 50 for MCP response-size budgets."
    },
    "query": {
      "type": "string",
      "examples": [
        "rust performance",
        "\"static analysis\"",
        "php or python"
      ],
      "description": "Search terms. AND-semantics by default; use `or` between terms for OR; wrap phrases in double quotes."
    },
    "format": {
      "enum": [
        "markdown",
        "html",
        "text"
      ],
      "type": "string",
      "default": "markdown",
      "description": "Output format for styledtext properties on the matched items. markdown is friendliest for AI consumption."
    },
    "locale": {
      "type": "string",
      "default": "",
      "description": "BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today."
    }
  },
  "additionalProperties": false
}

arguments 40 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 825742ba0c10ae59.

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

_ for your README measured, not declared

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