freudly-tests
Registry code: 7271cb26a6a82296
Freudly (freudly.ai) is a catalogue of psychological self-assessment tests in English, Spanish and Russian. Use search_tests to find tests that fit what the user is looking for, then get_test_info for the details of one test. Always give the user the `url` from the response: the test is taken on that page. Tests support self-reflection and screening, not diagnosis; if the user may be in crisis, point them to local emergency services first.
- endpoint
- https://freudly.ai/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 freudly-tests live?
- Yes — it answered the hub's last check (checked 7h ago). It answered 98% of checks over the last 30 days.
- Is freudly-tests free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does freudly-tests have?
- 2 tools: get_test_info, search_tests.
- Is freudly-tests 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.
90 days 99%· all time 99%
last good check
of 2 tools
- down → live
- degraded → down· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- used for
- find psychological self-assessment tests
- get details of a psychological test
- takes → gives
- text → data
- tools
- 2 reads
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.
through this hub
successful
what callers paid
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.
search_tests reads open 7h ago
Search the Freudly catalogue of psychological self-assessment tests (personality, anxiety, depression, burnout, relationships, IQ and more). Filter by keywords, topic, language (en, es, ru), maximum duration in minutes and maximum number of questions. Returns test ids, short summaries, duration, number of questions, topics and the URL where each test is taken.
{ "type": "object", "$defs": { "PublicLocale": { "enum": [ "en", "es", "ru" ], "type": "string" } }, "title": "PublicTestSearchParams", "properties": { "page": { "type": "integer", "title": "Page", "default": 1, "maximum": 50, "minimum": 1, "description": "Results page, starting at 1." }, "limit": { "type": "integer", "title": "Limit", "default": 10, "maximum": 20, "minimum": 1, "description": "Number of tests to return (1-20)." }, "query": { "anyOf": [ { "type": "string", "maxLength": 200 }, { "type": "null" } ], "title": "Query", "default": null, "description": "Keywords to match in test names and descriptions, written in the same language as `language` (e.g. \"anxiety\", \"burnout\", \"ansiedad\", \"тревога\"). Short keywords work better than sentences." }, "topic": { "anyOf": [ { "type": "string", "maxLength": 100 }, { "type": "null" } ], "title": "Topic", "default": null, "description": "Topic or theme in the same language as `language` (e.g. \"depression\", \"relationships\", \"personality\"). Matched against the catalogue topics; falls back to keyword search." }, "language": { "$ref": "#/$defs/PublicLocale", "default": "en", "description": "Language of the test and its page: en, es, or ru (ru has a small catalogue)." }, "max_minutes": { "anyOf": [ { "type": "integer", "maximum": 300, "minimum": 1 }, { "type": "null" } ], "title": "Max Minutes", "default": null, "description": "Maximum estimated duration, minutes." }, "max_questions": { "anyOf": [ { "type": "integer", "maximum": 1000, "minimum": 1 }, { "type": "null" } ], "title": "Max Questions", "default": null, "description": "Maximum number of questions." } }, "description": "Параметры search_tests — общие для REST и MCP." }arguments 96 linesget_test_info reads unknown 7h ago
Details of one Freudly test by id: description, instructions, the scales it measures, authors and sources, limitations, what the user needs to get the result, and the URL where the test is taken.
{ "type": "object", "$defs": { "PublicLocale": { "enum": [ "en", "es", "ru" ], "type": "string" } }, "title": "PublicTestInfoParams", "required": [ "test_id" ], "properties": { "test_id": { "type": "integer", "title": "Test Id", "minimum": 1, "description": "Test id from search_tests." }, "language": { "$ref": "#/$defs/PublicLocale", "default": "en", "description": "Language of the description: en, es, or ru." } }, "description": "Параметры get_test_info." }arguments 31 lines
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.
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, thenPOST /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-endpointwith this listing's id7271cb26a6a82296.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7271cb26a6a82296/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7271cb26a6a82296?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.