eGestor MCP by usefulapi
REMOTE · EGESTOR.USEFULAPI.IO
Read contacts, products, sales, receivables and payables; create contacts in eGestor.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://egestor.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of egestor.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://egestor.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/egestor/ |
| http (plaintext) | http://egestor.usefulapi.io/mcp | Inconclusive | 302 | http://egestor.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
egestor_create_contact Create a contact ~175
Create a new contact (customer, supplier or carrier) in eGestor. This writes data and is not idempotent: calling it twice creates two contacts. Returns the new code. eGestor API: POST /v1/contatos.
| Name | Type | Req | Description |
|---|---|---|---|
| cep | integer | – | Postal code (CEP), digits only. |
| cpfcnpj | string | – | CPF or CNPJ, digits only. |
| emails | array | – | Email addresses. |
| fantasia | string | – | Trade name. |
| fones | array | – | Phone numbers, digits only. |
| logradouro | string | – | Street. |
| nome | string | yes | Full name or company name. |
| numero | string | – | Street number. |
| tipo | array | yes | Contact kinds. |
| uf | string | – | State code, 2 letters. |
No output schema declared.
No examples provided.
egestor_get_company Get company data ~35
Get the registration data of the company that owns the token. eGestor API: GET /v1/empresa.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
egestor_get_contact Get a contact ~51
Get full data of one contact by code. eGestor API: GET /v1/contatos/{codigo}.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | integer | yes | The record code (from the matching list tool). |
No output schema declared.
No examples provided.
egestor_get_payable Get a payable ~49
Get one payable by code. eGestor API: GET /v1/pagamentos/{codigo}.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | integer | yes | The record code (from the matching list tool). |
No output schema declared.
No examples provided.
egestor_get_product Get a product ~51
Get full data of one product by code. eGestor API: GET /v1/produtos/{codigo}.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | integer | yes | The record code (from the matching list tool). |
No output schema declared.
No examples provided.
egestor_get_purchase Get a purchase ~48
Get full data of one purchase. eGestor API: GET /v1/compras/{codigo}.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | integer | yes | The record code (from the matching list tool). |
No output schema declared.
No examples provided.
egestor_get_receivable Get a receivable ~51
Get one receivable by code. eGestor API: GET /v1/recebimentos/{codigo}.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | integer | yes | The record code (from the matching list tool). |
No output schema declared.
No examples provided.
egestor_get_sale Get a sale ~66
Get full data of one sale: items, payments, totals. eGestor API: GET /v1/vendas/{codigo}.
| Name | Type | Req | Description |
|---|---|---|---|
| codigo | integer | yes | The record code (from the matching list tool). |
| listarCanceladas | boolean | – | Include cancelled sales. |
No output schema declared.
No examples provided.
egestor_list_accounts List financial accounts ~92
List cash boxes and bank accounts (disponiveis). eGestor API: GET /v1/disponiveis.
| Name | Type | Req | Description |
|---|---|---|---|
| filtro | string | – | Text search over the main fields of the record. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
No output schema declared.
No examples provided.
egestor_list_categories List categories ~85
List product and finance categories. eGestor API: GET /v1/categorias.
| Name | Type | Req | Description |
|---|---|---|---|
| filtro | string | – | Text search over the main fields of the record. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
No output schema declared.
No examples provided.
egestor_list_contacts List contacts ~122
List customers, suppliers and carriers. Good first call to find a contact code. eGestor API: GET /v1/contatos.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Comma-separated list of fields to return. |
| filtro | string | – | Text search over the main fields of the record. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
| tipo | string | – | Only this kind of contact. |
No output schema declared.
No examples provided.
egestor_list_payables List payables ~143
List accounts payable (situacao 10 = open, 30 = paid), filterable by date range. eGestor API: GET /v1/pagamentos.
| Name | Type | Req | Description |
|---|---|---|---|
| dtFim | string | – | End date yyyy-mm-dd. |
| dtIni | string | – | Start date yyyy-mm-dd. |
| filtro | string | – | Text search over the main fields of the record. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
| situacao | – | – | 10 = open, 30 = paid. |
No output schema declared.
No examples provided.
egestor_list_products List products ~102
List products with prices and stock data. eGestor API: GET /v1/produtos.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Comma-separated list of fields to return. |
| filtro | string | – | Text search over the main fields of the record. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
No output schema declared.
No examples provided.
egestor_list_purchases List purchases ~185
List purchases (situacao 10 = quote, 50 = confirmed), filterable by date range. eGestor API: GET /v1/compras.
| Name | Type | Req | Description |
|---|---|---|---|
| dtFim | string | – | End date yyyy-mm-dd. |
| dtIni | string | – | Start date yyyy-mm-dd. |
| dtTipo | string | – | Which date field dtIni/dtFim filter on. |
| fields | string | – | Comma-separated list of fields to return. |
| filtro | string | – | Text search over the main fields of the record. |
| nota | string | – | Filter by invoice number. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
| situacao | – | – | 10 = quote, 50 = confirmed. |
No output schema declared.
No examples provided.
egestor_list_receivables List receivables ~146
List accounts receivable (situacao 20 = open, 40 = received), filterable by date range. eGestor API: GET /v1/recebimentos.
| Name | Type | Req | Description |
|---|---|---|---|
| dtFim | string | – | End date yyyy-mm-dd. |
| dtIni | string | – | Start date yyyy-mm-dd. |
| filtro | string | – | Text search over the main fields of the record. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
| situacao | – | – | 20 = open, 40 = received. |
No output schema declared.
No examples provided.
egestor_list_sales List sales ~189
List sales (situacao 10 = quote, 50 = sale), filterable by date range and contact. eGestor API: GET /v1/vendas.
| Name | Type | Req | Description |
|---|---|---|---|
| codContato | integer | – | Only sales of this contact code. |
| dtFim | string | – | End date yyyy-mm-dd. |
| dtIni | string | – | Start date yyyy-mm-dd. |
| dtTipo | string | – | Which date field dtIni/dtFim filter on. |
| fields | string | – | Comma-separated list of fields to return. |
| filtro | string | – | Text search over the main fields of the record. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
| situacao | – | – | 10 = quote, 50 = sale. |
No output schema declared.
No examples provided.
egestor_list_services List services ~85
List services the company sells. eGestor API: GET /v1/servicos.
| Name | Type | Req | Description |
|---|---|---|---|
| filtro | string | – | Text search over the main fields of the record. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
No output schema declared.
No examples provided.
egestor_list_users List users ~114
List users and sales people of the account. eGestor API: GET /v1/usuarios.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Comma-separated list of fields to return. |
| filtro | string | – | Text search over the main fields of the record. |
| orderBy | string | – | Sort as "field,asc" or "field,desc". |
| page | integer | – | Page number (default 1, 50 rows per page). |
| vendedor | boolean | – | true = only sales people. |
No output schema declared.
No examples provided.
How do I install the eGestor MCP by usefulapi server?
eGestor MCP by usefulapi is a hosted endpoint at https://egestor.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · egestor.usefulapi.io
claude mcp add --transport http io-usefulapi-egestor 'https://egestor.usefulapi.io/mcp'
What is the eGestor MCP by usefulapi server?
eGestor MCP by usefulapi is listed in the public MCP registry as io.usefulapi/egestor. Read contacts, products, sales, receivables and payables; create contacts in eGestor. This page covers its hosted endpoint (https://egestor.usefulapi.io/mcp).
Is the eGestor MCP by usefulapi server safe to use?
eGestor MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the eGestor MCP by usefulapi server expose?
eGestor MCP by usefulapi exposes 18 tools: egestor_list_contacts, egestor_get_contact, egestor_create_contact, egestor_list_products, egestor_get_product, and 13 more. Their descriptions and schemas cost roughly 1,789 tokens of context every time the server is loaded.
Does the eGestor MCP by usefulapi server require authentication?
Its publisher declares no required credentials for eGestor MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the eGestor MCP by usefulapi server still maintained?
eGestor MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the eGestor MCP by usefulapi server?
VerifyMCP ran 4 checks on eGestor MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about eGestor MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.