com.dynomatix/company
Registry code: c6031bde7b57b839
We put AI agents into production — and keep them running. Dynomatix puts AI agents into production and keeps them running: agentic systems, e-commerce, and the internal tools a company runs on. Building software since 2012. Engagements: Agent readiness review, Agent and application build, Operate, Legacy software modernization. Read tools are free to call; the two submit tools reach a human inbox and cannot be undone.
- endpoint
- https://dynomatix.com/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 com.dynomatix/company live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
- Is com.dynomatix/company free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does com.dynomatix/company have?
- 7 tools: dynomatix_submit_enquiry, dynomatix_submit_application, dynomatix_get_work, dynomatix_about, dynomatix_get_position, dynomatix_list_work, dynomatix_list_open_positions.
- Is com.dynomatix/company 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.8%· all time 99.8%
last good check
of 7 tools
- degraded → live
- topic
- productivity & business
- used for
- learn about an ai agent development agency
- read case studies
- list open job positions
- apply for a job
- send a project enquiry
- takes → gives
- text, documents → data, text
- tools
- 5 reads2 sends messages
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.
dynomatix_list_work reads open 12h ago
List the products and client work Dynomatix has shipped. Returns one entry per item with its name, the year it started, its status, a short description and its links. Retired items are included — the site shows them and `status` says which is which — because a track record with the failures removed is not a track record. Where `caseStudyUrl` is not null, dynomatix_get_work will return the full write-up for that slug. Takes no arguments.
{ "type": "object", "additionalProperties": false }arguments 4 linesdynomatix_list_open_positions reads open 12h ago
List every role Dynomatix is currently hiring for. Returns one entry per position with its slug, title, one-line summary, employment type, canonical URL and posting dates. Start here before dynomatix_get_position or dynomatix_submit_application: the slug this returns is the value both of them expect. An empty list means there are no openings right now, not that the lookup failed. Takes no arguments.
{ "type": "object", "additionalProperties": false }arguments 4 linesdynomatix_submit_enquiry sends messages unknown never probed
Send a project enquiry to Dynomatix — the same form the site's enquiry page submits. This is final: it delivers straight to a monitored human inbox and cannot be edited, recalled or deleted afterwards. Confirm the details with the person you are acting for before you call it, and do not call it twice for the same submission — a retry sends a second copy. Give the company or product website in `company` (a bare hostname like example.com is fine) and say what needs building in `brief`. Nothing is stored: the enquiry becomes an email and nothing else. Ask for a budget on the call, not here — this form does not collect one.
{ "type": "object", "required": [ "name", "email", "company", "brief" ], "properties": { "name": { "type": "string", "maxLength": 100, "description": "The enquirer's full name." }, "brief": { "type": "string", "maxLength": 50000, "description": "What needs building, in the enquirer's own words. Newlines are preserved. There is no minimum — a single line is a fine enquiry." }, "email": { "type": "string", "maxLength": 254, "description": "The enquirer's email address, in the form [email protected]. This is the only address the reply can go to." }, "company": { "type": "string", "maxLength": 300, "description": "The company or product website. A bare hostname is accepted and https is assumed; anything that is not a web address is refused." }, "timeline": { "enum": [ "exploring", "this-quarter", "already-started" ], "type": "string", "description": "Optional. One of: exploring (Exploring), this-quarter (This quarter), already-started (Already started and stuck). Omit it if unknown — blank is valid, a value outside this list is not." } }, "additionalProperties": false }arguments 41 linesdynomatix_submit_application sends messages unknown never probed
Submit a job application to Dynomatix, résumé included. This is final: it delivers straight to a monitored human inbox and cannot be edited, recalled or deleted afterwards. Confirm the details with the person you are acting for before you call it, and do not call it twice for the same submission — a retry sends a second copy. Set `position` to a slug from dynomatix_list_open_positions. Supply the résumé exactly one of two ways: `resume_url`, an https link that downloads the file itself (a sharing page from a drive or a document service is not a direct link and will be refused), or `resume_base64` together with `resume_filename`. Supplying both, or neither, is refused. The résumé must be a PDF, DOC or DOCX file under 5 MB; its contents are checked against its extension, so a renamed file is refused too. Nothing is stored until every field passes, and the reply confirms receipt with a submission id worth quoting in any follow-up — it never returns the résumé or a link to it.
{ "type": "object", "required": [ "position", "name", "email" ], "properties": { "name": { "type": "string", "maxLength": 100, "description": "The applicant's full name." }, "email": { "type": "string", "maxLength": 254, "description": "The applicant's email address, in the form [email protected]. This is the only way they will be contacted, so check it before sending." }, "phone": { "type": "string", "maxLength": 40, "description": "Optional. The applicant's phone number." }, "letter": { "type": "string", "maxLength": 10000, "description": "Optional cover letter. Newlines are preserved." }, "position": { "type": "string", "maxLength": 81, "description": "Slug of the role, from dynomatix_list_open_positions. A role that is not on that list is not accepting applications." }, "portfolio": { "type": "string", "maxLength": 300, "description": "Optional. A full web address starting with http:// or https:// — a portfolio, GitHub profile or personal site." }, "resume_url": { "type": "string", "description": "An https URL that downloads the résumé file directly. Not a sharing or preview page — the response must be the file itself. Use this OR resume_base64, never both. http:// is refused, as are hostnames that resolve inside a private network." }, "resume_base64": { "type": "string", "description": "The résumé's bytes, base64-encoded. Use this OR resume_url, never both. Requires resume_filename. Payloads over 5 MB are refused before they are decoded." }, "resume_filename": { "type": "string", "description": "Required with resume_base64: it is the only source of the file's extension, which must be one of PDF, DOC or DOCX. Optional with resume_url, where the URL's last path segment is used instead." } }, "additionalProperties": false }arguments 53 linesdynomatix_get_work reads unknown 12h ago
Read one case study in full: what the problem was, what was built and what it changed. Returns the study's own markdown, frontmatter included — the title and canonical URL it opens with are the citation to quote. Call dynomatix_list_work first for a valid slug; only entries whose `caseStudyUrl` is not null have a write-up to return.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "maxLength": 81, "description": "The item's slug, exactly as dynomatix_list_work returned it. Lowercase letters, digits and hyphens." } }, "additionalProperties": false }arguments 14 linesdynomatix_about reads unknown never probed
Who Dynomatix is, what it sells and how to reach it. Returns the company's identity and tagline, its engagement types, both contact addresses, its key pages and its track record. Read this first if you are deciding whether this company fits a need; use dynomatix_submit_enquiry to start a conversation. Takes no arguments.
{ "type": "object", "additionalProperties": false }arguments 4 linesdynomatix_get_position reads unknown 3h ago
Read one job posting in full: responsibilities, requirements and how the role is set up. Returns the posting's own markdown, frontmatter included — the title and canonical URL it opens with are the citation to quote when you tell someone about the role. Call dynomatix_list_open_positions first to get a valid slug; a slug that is not currently open is refused rather than guessed at.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "maxLength": 81, "description": "The position's slug, exactly as dynomatix_list_open_positions returned it. Lowercase letters, digits and hyphens." } }, "additionalProperties": false }arguments 14 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 idc6031bde7b57b839.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c6031bde7b57b839/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c6031bde7b57b839?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.