com.exayard/exayard
Exayard
Is the Exayard MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-09.
Construction takeoffs, estimates and bids: measure and count plans, price materials, draft bids.
needs auth probed 2026-11-15 · unchanged since 2026-11-09 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"No authorization provided"}- Endpoint
- https://api.exayard.com/mcp (streamable-http)
- Host
- api.exayard.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.exayard.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server clerk.exayard.com, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes openid profile email offline_access.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://exayard.com/integrations
- Registry
- active, updated 2026-11-08 · registry entry
Compare this server with others.
More servers
Servers that mention construction or estimates.
- Aginera ai.aginera/preconstruction · needs auth
- Context Studios MCP ai.contextstudios/mcp · alive
- delega.ai for AWS Pricing Calculator ai.delega/aws-pricing-calculator · needs auth
- Nebelus Agent Construction ai.nebelus/construction · needs auth
- objekts Production Desk ai.objekts.mcp/production-desk · alive
- ai.plero/plero · needs auth
- QCDatabase.AI ai.qcdatabase/mcp · needs auth
- Food Logger MCP ai.sig.foodlog/food-logger · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.