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

RIX Freight MCP (multilingual)

https://mcp.rixfreight-group.com

Registry code: c4d499c664171e82

api record

RixFreight logistics quotes and route info via AI agents

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.rixfreight-group.com/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 RIX Freight MCP (multilingual) live?
No — it has stopped answering the hub's checks (checked 25h ago). It answered 35% of checks over the last 30 days.
Is RIX Freight MCP (multilingual) free to use?
Yes — the hub reached it with no key and no payment.
What tools does RIX Freight MCP (multilingual) have?
8 tools: create_inquiry, get_service, get_route, get_services, get_company_info, list_routes, list_languages, get_faq.
Is RIX Freight MCP (multilingual) 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
retired
uptime, 30 days
35%

90 days 64.3%· all time 64.3%

latency
108ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 263 checks · signed record
  • down → retired· fetch failed
  • degraded → down· fetch failed
  • live → degraded· fetch failed
  • degraded → live
  • degraded → live
_ what it is for
topic
maps travel & places logistics & shipping
used for
  • list freight routes
  • get freight service details
  • read moving and freight faq
  • submit a freight inquiry
takes → gives
text → data, text
tools
7 reads1 sends messages
_ 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 8 tools
6 open 2 never probed 6 of 8 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_route reads open 23d ago

    Find a freight route by origin and/or destination country (English country names), localized to lang.

    mcp-tool

    {
  "type": "object",
  "title": "get_routeArguments",
  "properties": {
    "lang": {
      "type": "string",
      "title": "Lang",
      "default": ""
    },
    "origin": {
      "type": "string",
      "title": "Origin",
      "default": ""
    },
    "language": {
      "type": "string",
      "title": "Language",
      "default": ""
    },
    "destination": {
      "type": "string",
      "title": "Destination",
      "default": ""
    }
  }
}
    arguments 26 lines
  • get_services reads open 22d ago

    List RIX Freight services/offerings, localized to lang (en,lv,lt,et,de,fr,es,it,pl,ru,uk,fi,sv,nb).

    mcp-tool

    {
  "type": "object",
  "title": "get_servicesArguments",
  "properties": {
    "lang": {
      "type": "string",
      "title": "Lang",
      "default": ""
    },
    "language": {
      "type": "string",
      "title": "Language",
      "default": ""
    }
  }
}
    arguments 16 lines
  • get_company_info reads open 23d ago

    Company info + how to get in touch.

    mcp-tool

    {
  "type": "object",
  "title": "get_company_infoArguments",
  "properties": {
    "lang": {
      "type": "string",
      "title": "Lang",
      "default": ""
    },
    "language": {
      "type": "string",
      "title": "Language",
      "default": ""
    }
  }
}
    arguments 16 lines
  • list_routes reads open 23d ago

    List freight routes (origin to destination country pairs) RIX Freight serves, localized to lang.

    mcp-tool

    {
  "type": "object",
  "title": "list_routesArguments",
  "properties": {
    "lang": {
      "type": "string",
      "title": "Lang",
      "default": ""
    },
    "language": {
      "type": "string",
      "title": "Language",
      "default": ""
    }
  }
}
    arguments 16 lines
  • list_languages reads open 22d ago

    Supported languages for RIX Freight content.

    mcp-tool

    {
  "type": "object",
  "title": "list_languagesArguments",
  "properties": {}
}
    arguments 5 lines
  • get_faq reads open 22d ago

    General moving/freight FAQ in English: deposit and payment terms, insurance, typical timelines, and what's included in a standard move.

    mcp-tool

    {
  "type": "object",
  "title": "get_faqArguments",
  "properties": {}
}
    arguments 5 lines
  • create_inquiry sends messages unknown never probed

    Submit an inquiry to RIX Freight. Records the MCP channel and which AI agent submitted it. Set ai_agent to your own model/assistant name (for example 'ChatGPT' or 'Claude'). Set test=true to preview the payload with no email/network side effects.

    mcp-tool

    {
  "type": "object",
  "title": "create_inquiryArguments",
  "required": [
    "full_name",
    "email",
    "message"
  ],
  "properties": {
    "test": {
      "type": "boolean",
      "title": "Test",
      "default": false
    },
    "email": {
      "type": "string",
      "title": "Email"
    },
    "phone": {
      "type": "string",
      "title": "Phone",
      "default": ""
    },
    "company": {
      "type": "string",
      "title": "Company",
      "default": ""
    },
    "message": {
      "type": "string",
      "title": "Message"
    },
    "ai_agent": {
      "type": "string",
      "title": "Ai Agent",
      "default": ""
    },
    "full_name": {
      "type": "string",
      "title": "Full Name"
    }
  }
}
    arguments 43 lines
  • get_service reads unknown 22d ago

    Get one service/page by name or slug, localized to lang.

    mcp-tool

    {
  "type": "object",
  "title": "get_serviceArguments",
  "required": [
    "query"
  ],
  "properties": {
    "lang": {
      "type": "string",
      "title": "Lang",
      "default": ""
    },
    "query": {
      "type": "string",
      "title": "Query"
    },
    "language": {
      "type": "string",
      "title": "Language",
      "default": ""
    }
  }
}
    arguments 23 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 c4d499c664171e82.

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