# TCC Group website

> Read-only tools for tcc.group: contact card, documents, page search and page content.

- name: group.tcc/website
- version: 1.4.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 100/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/group.tcc%2Fwebsite
- tools: https://api.protogrid.dev/v1/servers/group.tcc%2Fwebsite/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "website": {
      "type": "http",
      "url": "https://mcp.tcc.group"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-11d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 100/100 (strong)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 300000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 18 of 18 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 2,646 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name
- pass `stability.new_links`: no tool change named a new site

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 18, about 2,646 tokens to load them all
- tool set hash: 9c3d340720151f6b63f15d49a3b98065
- badge: [![protogrid quality](https://protogrid.dev/badge/group.tcc/website.svg)](https://protogrid.dev/servers/group.tcc/website)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.tcc.group (streamable-http, auth none, reachable true, uptime30d 1)
- https://tcc.group/wp-json/tcc-mcp/v1/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (18)

- `get_citation_links`: Return clean source links and markdown citation bullets for a query context.
- `get_contact_card`: Use this when a person asks how to get in touch with this organisation and would like to see it as a card: it shows the same facts as get_contact_options, which are the address of its contact page, the enquiry routes that page offers, and the email address, telephone number and office hours the site publishes, with a button that opens the contact page. A fact the site does not publish is left out, and hours and routes are stated as the site publishes them, not as a promise of availability or of a response time. Takes no arguments, accepts no personal data and sends nothing: the person completes any enquiry on the contact page themselves. A client that does not show cards receives the same answer as text.
- `get_contact_options`: Get how a person can contact this organisation: the address of its contact page, the enquiry routes that page offers, and the email address, telephone number and office hours the site publishes. Use it when a person asks how to get in touch. A fact the site does not publish is left out, and hours and routes are stated as the site publishes them, not as a promise of availability or of a response time. Takes no arguments, accepts no personal data and sends nothing: the person completes any enquiry on the contact page themselves.
- `get_document`: Get one public document card, with its schema.org node, by the id that search_documents returns. A document that does not exist or is not published for this website returns the same not-found answer.
- `get_document_carousel`: Use this when a person wants to see documents that search_documents or get_document returned: it shows up to three of them as a carousel of cards, each with the document's title, summary, size, number of pages and preview image, a button that opens the PDF and a link to contact the organisation. Pass the id of each document to show, taken from the id of its card, at most three. A document that is not published for this website is left out, and when none can be shown the answer is the one get_document gives for a document that is not found. Do not use it to find documents: call search_documents for that. A client that does not show cards receives the same answer as text.
- `get_navigation`: Return the primary navigation structure.
- `get_page_content_with_schema`: Get full page textual content and published JSON-LD schema for grounded evaluation.
- `get_person_profile`: Get one published team member profile and its schema.org Person JSON-LD by slug.
- `get_schema_context`: Return the sitewide Organization schema context.
- `get_site_info`: Get site metadata and MCP server capabilities.
- `get_team_directory`: Get the published, featured team member directory (Core-managed People profiles). Read-only and published-only, like every other tool.
- `list_pages`: List published WordPress pages with pagination.
- `list_posts`: List published posts, insights, or case studies, optionally filtered by taxonomy.
- `list_taxonomy_terms`: List published taxonomy terms with counts.
- `search_content`: Search public pages, posts, insights, and case studies.
- `search_documents`: Search the public documents (PDF files) that this website publishes and return each as a document card with its schema.org node. Filter by topic or sector (slugs), by the address of a page on this website to find the documents related to it, or search by phrase. Call get_document to open one document by its id. Only published, open documents appear, and none may be available.
- `search_enriched_page_contexts`: Search site content and return top matching page contexts enriched with full text and JSON-LD schema.
- `search_media_assets`: Search public, active Core-managed Media Assets eligible for this website and return safe delivery variants plus schema.org MediaObject JSON-LD. Private and management records are never returned, and neither are documents that the website's editorial mapping gates, nor any document while that mapping cannot be read.