com.ainecto/mcp
AiNecto
Is the AiNecto MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Shared project memory for people and AI agents: documents, ERD, diagrams, boards, design mockups.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_request","error_description":"Bearer token required"}- Endpoint
- https://ainecto.com/mcp (streamable-http)
- Host
- ainecto.com
- Package
- The publisher's package npm:@ainecto/mcp did not list its tools in the container: needs network, MCP error -32603: fetch failed.
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://ainecto.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 ainecto.com, PKCE S256, grants authorization_code, refresh_token.
Scopes openid profile email mcp.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/codelives/ainecto
- Website
- https://ainecto.com/en/?utm_source=mcpregistry&utm_medium=referral&utm_campaign=agent-directory
- Registry
- active, updated 2026-11-07 · registry entry
Compare this server with others.
More servers
Servers that mention ainecto or documents or diagrams.
- AiNecto io.github.codelives/ainecto · crashed on start
- AutEng MCP - Markdown Publishing & Document Share Links ai.auteng/mcp · alive
- DiagramZu ai.diagramzu/mcp · needs auth
- ai.extend/extend · needs auth
- ai.ezel/ezel · needs auth
- ai.filegraph/document-processing · not found
- FinStat ai.finstat/finstat · needs auth
- ai.jeda/jeda-ai · alive
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.