app.awsel/wafeq
Wafeq Connector (Awsel)
Is the Wafeq Connector (Awsel) MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
Turn chat invoices into drafts in Wafeq accounting. 17 tools, OAuth sign-in, human approval.
needs auth probed 2026-11-15 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error": "unauthorized"}- Endpoint
- https://wafeq.awsel.app/mcp (streamable-http)
- Host
- wafeq.awsel.app
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://wafeq.awsel.app/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server wafeq.awsel.app, PKCE S256, grants authorization_code, refresh_token.
Scopes wafeq.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://awsel.app/wafeq/
- Registry
- active, updated 2026-11-10 · registry entry
- Changes
- 3 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention wafeq or connector or awsel.
- Wafeq io.github.ohneben/wafeq-mcp · alive
- Elaichi ai.elaichi/mcp · needs auth
- LensHub ai.lenshub/lenshub · needs auth
- PDS Project AI MPP Connector ai.projectdata/mpp-connector · needs auth
- ProvenSkills Labs ai.provenskills/labs · needs auth
- Era Context app.era/context · needs auth
- Lucid app.lucid.mcp/lucid · needs auth
- Fedlex Connector ch.fedlex-connector/fedlex-connector · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-11 11:03 | needs auth | ||||
| 2026-11-10 11:18 | not found | ||||
| 2026-10-28 09:43 | 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.