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

naia-pages-mcp

https://blog.naia.today

Registry code: 8636b27e1b053d37

api record

Searches and returns articles, guides and FAQs published on the Naia blog, along with basic information about the site and company.

endpoint
https://blog.naia.today/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 naia-pages-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is naia-pages-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does naia-pages-mcp have?
6 tools: ask, search_chunks, get_content, get_site_info, list_content_types, search_content.
Is naia-pages-mcp 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
97.6%

90 days 98.3%· all time 98.3%

latency
631ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 414 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
knowledge & reference
used for
  • search blog articles
  • ask a question about site content
  • get a full article
takes → gives
text → data, text
tools
6 reads
_ 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

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

  • get_site_info reads open 15h ago

    Retorna informações sobre o site e a empresa: nome, categoria, localização geográfica, nicho de atuação, descrição e endpoints de descoberta.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_content_types reads open 19h ago

    Lista os tipos de conteúdo disponíveis no site, com contagem de artigos publicados em cada categoria.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_content reads open 19h ago

    Busca conteúdo publicado no site por termo, tipo ou palavra-chave. Retorna título, resumo, tipo, URL e data de publicação.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Número máximo de resultados, com padrão de 20 e máximo de 50."
    },
    "query": {
      "type": "string",
      "description": "Termo de busca, com busca em título, descrição e palavra-chave."
    },
    "content_type": {
      "enum": [
        "blog",
        "faq",
        "guia",
        "comparativo",
        "case_study",
        "landing"
      ],
      "type": "string",
      "description": "Filtrar por tipo de conteúdo. Use blog para conteúdos em Insights."
    }
  }
}
    arguments 25 lines
  • ask reads unknown 19h ago

    Endpoint NLWeb para perguntas em linguagem natural sobre o site. Retorna resultados ranqueados em JSON-LD Schema.org (SearchResultsPage). Equivale ao endpoint público /ask, sem custo de LLM.

    mcp-tool

    {
  "type": "object",
  "required": [
    "question"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "description": "Máximo de resultados, com padrão de 5 e máximo de 10."
    },
    "question": {
      "type": "string",
      "description": "Pergunta em linguagem natural, com máximo de 200 caracteres."
    },
    "content_type": {
      "enum": [
        "blog",
        "faq",
        "guia",
        "comparativo",
        "case_study",
        "landing"
      ],
      "type": "string",
      "description": "Filtrar por tipo de conteúdo, de forma opcional. Use blog para conteúdos em Insights."
    }
  }
}
    arguments 28 lines
  • search_chunks reads unknown 15h ago

    Busca semântica em chunks de conteúdo com ranking de relevância. Ideal para encontrar trechos específicos sobre um tópico. Cada chunk tem de 100 a 400 tokens, com foco em um único subtópico.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "description": "Número máximo de chunks, com padrão de 10 e máximo de 50."
    },
    "query": {
      "type": "string",
      "description": "Termo de busca em full-text search em português."
    },
    "content_type": {
      "enum": [
        "blog",
        "faq",
        "guia",
        "comparativo",
        "case_study",
        "landing"
      ],
      "type": "string",
      "description": "Filtrar por tipo de conteúdo. Use blog para conteúdos em Insights."
    }
  }
}
    arguments 28 lines
  • get_content reads unknown 15h ago

    Retorna o conteúdo completo, em texto, de um artigo, guia, FAQ ou outro conteúdo publicado a partir do slug.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Slug, o identificador de URL do conteúdo."
    }
  }
}
    arguments 12 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 8636b27e1b053d37.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8636b27e1b053d37/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/8636b27e1b053d37/badge.svg)](https://brick.blue/agent/8636b27e1b053d37?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.

_ also on naia.today 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.