_ registry / mcp http-sse · checked 13h ago

g3apply-public

https://apply.g3infotech.app

Registry code: fc65ac710f25e16d

api record

Servidor MCP público e só de leitura do G3 Apply, o copilot de candidaturas da G3 Infotech. Ele responde o que é o produto, como funciona, os planos e preços, as perguntas frequentes, os posts do blog e os links para criar conta. Não acessa conta, dado pessoal nem o app autenticado, e nenhuma ferramenta altera nada. Toda ferramenta aceita o idioma da resposta: pt-BR, en ou es.

endpoint
https://apply.g3infotech.app/mcp
protocol
http-sse ·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 g3apply-public live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is g3apply-public free to use?
Yes — the hub reached it with no key and no payment.
What tools does g3apply-public have?
7 tools: get_faq, list_blog_posts, get_signup_links, get_blog_post, get_how_it_works, get_plans_and_pricing, get_product_overview.
Is g3apply-public 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
291ms

last good check

priced tools
0

of 7 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

_ what it can do 7 tools
3 open 4 never probed 3 of 7 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_how_it_works open 13h ago

    Os passos do G3 Apply, da configuração do copilot até a revisão e o envio da candidatura.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "locale": {
          "enum": [
            "pt-BR",
            "en",
            "es"
          ],
          "type": "string",
          "description": "Idioma da resposta: pt-BR, en ou es. Sem ele, vale o Accept-Language da requisição e, na falta dele, pt-BR."
        }
      }
    }
    arguments 15 lines
  • get_plans_and_pricing open 13h ago

    Planos do G3 Apply com os preços mensal e trimestral na moeda indicada em currency (real em português, dólar nos outros idiomas), a economia do trimestral, os limites de cada plano e o que vem em todos eles.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "locale": {
          "enum": [
            "pt-BR",
            "en",
            "es"
          ],
          "type": "string",
          "description": "Idioma da resposta: pt-BR, en ou es. Sem ele, vale o Accept-Language da requisição e, na falta dele, pt-BR."
        }
      }
    }
    arguments 15 lines
  • get_product_overview open 13h ago

    Resumo público do G3 Apply: o que o copilot faz, os recursos incluídos na conta, o que esperar da revisão antes do envio e os links do site.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "locale": {
          "enum": [
            "pt-BR",
            "en",
            "es"
          ],
          "type": "string",
          "description": "Idioma da resposta: pt-BR, en ou es. Sem ele, vale o Accept-Language da requisição e, na falta dele, pt-BR."
        }
      }
    }
    arguments 15 lines
  • get_faq unknown never probed

    As perguntas frequentes da página do G3 Apply, com as respostas.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "locale": {
          "enum": [
            "pt-BR",
            "en",
            "es"
          ],
          "type": "string",
          "description": "Idioma da resposta: pt-BR, en ou es. Sem ele, vale o Accept-Language da requisição e, na falta dele, pt-BR."
        }
      }
    }
    arguments 15 lines
  • list_blog_posts unknown never probed

    Lista dos posts publicados no blog do G3 Apply no idioma pedido, do mais recente para o mais antigo. A lista vem vazia enquanto não houver post publicado.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "locale": {
          "enum": [
            "pt-BR",
            "en",
            "es"
          ],
          "type": "string",
          "description": "Idioma da resposta: pt-BR, en ou es. Sem ele, vale o Accept-Language da requisição e, na falta dele, pt-BR."
        }
      }
    }
    arguments 15 lines
  • get_signup_links unknown never probed

    Endereços para criar uma conta grátis, entrar e abrir o site do G3 Apply.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "locale": {
          "enum": [
            "pt-BR",
            "en",
            "es"
          ],
          "type": "string",
          "description": "Idioma da resposta: pt-BR, en ou es. Sem ele, vale o Accept-Language da requisição e, na falta dele, pt-BR."
        }
      }
    }
    arguments 15 lines
  • get_blog_post unknown never probed

    Conteúdo completo de um post do blog do G3 Apply, em Markdown, pelo identificador que aparece em list_blog_posts.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
          "maxLength": 120,
          "minLength": 1,
          "description": "Identificador do post, como aparece em list_blog_posts."
        },
        "locale": {
          "enum": [
            "pt-BR",
            "en",
            "es"
          ],
          "type": "string",
          "description": "Idioma da resposta: pt-BR, en ou es. Sem ele, vale o Accept-Language da requisição e, na falta dele, pt-BR."
        }
      }
    }
    arguments 25 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 fc65ac710f25e16d.

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