io.github.nvlsoft-ca/nexos

Nexos

Is the Nexos MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.

Work tracker for teams: create, triage, and update issues, projects, and milestones as yourself.

needs auth probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint:

Endpoint: https://mcp.nexos.ca/mcp (streamable-http)
Host: mcp.nexos.ca
Getting access: OAuth without dynamic client registration. Ask the publisher for a client id first; with it, a client can run the consent.
Authorization server 93e5cb54-6f3e-4125-96a5-3db447da7f91.ciamlogin.com, grants authorization_code.
Scopes api://a7fc289a-67f6-44ab-8be1-05ad0c791211/nexo.access.
Read from the server's public OAuth metadata, without a token. Method.
Repository: https://github.com/nvlsoft-ca/nexos-codex
Website: https://nexos.ca
Registry: active, updated 2026-11-13 · registry entry

More servers

Servers that mention milestones or projects.

Dubai Data — Dubai real estate statistics ae.datadubai/dubai-real-estate · alive
Alpic ai.alpic.mcp/alpic-mcp · needs auth
Atako ai.atako/mcp · needs auth
Project Desk ai.atlier/project-desk · needs auth
AutoRFP.ai ai.autorfp/mcp · needs auth
BeatBandit MCP ai.beatbandit/beatbandit · needs auth
ai.bridgeapp/bridgeapp · needs auth
Data Center Index ai.datacenterindex/datacenterindex · needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

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.