This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.obviouy.com
33tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.obviouy.com/mcp
Skill page: https://www.mcpbundles.com/skills/obviouy-mcp-f554aafc8f
Explore capabilities (33)
read 24
write 1
Showing 25 of 33
Showing 25 of 33 tools from the public preview. Connect the server to inspect the full live tool list.
Get10
List10
Search3
Other capabilities2
List trademarks
read
list_trademarks
The trademark collection with simple filters — and the BATCH inside it. Read-only. Identical to REST GET /trademarks.
Filters: `q` (free text), `applicationNumber` (a LIST — this is the batch, up to 100), `niceClass`, `status`, `signType`, `holder` / `representative` / `taxId` (all three are LISTS, OR within the parameter — 'marks of ACME or of Beta' is one query, not two), `denomination`, `registrationNumber`, the four date ranges (`filedFrom`/`filedTo`, `expiresFrom`/`expiresTo`, `registeredF
Description may be truncated on the public preview.
List trademarks — The trademark collection with simple filters — and the BATCH inside it. Read-only. Identical to REST GET /trademarks.
Filters: `q` (free text), `applicationNumber` (a LIST — this is the batch, up to 100), `niceClass`, `status`, `signType`, `holder` / `representative` / `taxId` (all three are LISTS, OR within the parameter — 'marks of ACME or of Beta' is one query, not two), `denomination`, `registrationNumber`, the four date ranges (`filedFrom`/`filedTo`, `expiresFrom`/`expiresTo`, `registeredF
Search trademarks (similarity, opposition window, long lists) — The trademark search for everything that GROWS: similarity, the opposition window, and filter lists too long for a URL. Read-only. Identical to REST POST /trademarks/search. It takes the SAME filters as `list_trademarks` and returns the SAME shape, plus three that choose an engine:
· `similarTo` — free text. Ranked by a 3-channel weighted-RRF engine (lexical BM25, trigram, vector), not by substring matching.
· `similarToTrademark` — an EXISTING mark by its application number. ⚠ NOT the same que
Get one trademark, with optional expansion — Fetch ONE trademark by its application number. Read-only. Identical to REST GET /trademarks/{applicationNumber}. An unknown application number returns a structured not_found (mirroring REST's 404).
⭐ THE REPORT IS NOT A SEPARATE CALL any more: ask for its sections with `expand: ["parties", "annotations", "encumbrances", "classes", "norms"]`. The old detail/report split declared the SAME fields with two different null semantics, so a typed client could not share one model between the two views —
Get one annotation by its identifier — Fetch ONE annotation — one act recorded against a trademark — by its identifier. Read-only. Identical to REST GET /annotations/{id}.
⭐ This is what makes an annotation a thing you can REFER TO. Until this contract, acts were only readable inside a mark and the opposition timeline published them without any identifier at all, so a caller could read 'an opposition was filed on 3 March' and had no way to cite that act — not to fetch it, not to quote it in a ticket, not to join it to the 1.5 M norm
List the annotations of one trademark — List the acts recorded against ONE trademark, newest filter first, in chronological order (`fecha` ascending). Read-only. Identical to REST GET /trademarks/{applicationNumber}/annotations.
⭐ REPLACES the former `get_brand_opposition`: the opposition timeline was always a FILTER over the annotations, so ask for it with `family: "opposition"`. Publishing it as a tool of its own meant inventing another tool every time someone wanted another family.
Filters: `family` (the act family — `opposition`
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Obviouy is an MCP server at mcp.obviouy.com. MCPBundles discovered 33 tools on the live endpoint.
How do I connect Obviouy to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does Obviouy provide?
Operate this server?
Request removal if you do not want Obviouy listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Obviouy?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
Search annotations across trademarks — Search acts ACROSS trademarks — the question the corpus could answer for 1.5 M citations and the contract gave no way to ask: *which resolutions cite article 20 letter h?* Read-only. Identical to REST POST /annotations/search.
Filters: `family` (the act family — `opposition` is the procedural timeline that used to be a route of its own; `publication`, `renewal`, `payment`, `transfer` are the other named ones, and any other value is passed through to the catalogue), `section` (INAPI's own sectio
Aggregate the trademark corpus by one dimension — The trademark corpus aggregated by ONE dimension — `groupBy` is filedMonth|status|niceClass|holder|representative — and every dimension returns the SAME element shape { key, label (es-CL/en/pt-BR), count }. Read-only. Identical to REST GET /insights/trademarks?groupBy=… Every filter of list_trademarks is APPLIED with the same semantics (lists are OR). `q` counts the marks whose denomination contains every token of `q` (accent-insensitive: the search's exact lexical channel, without its 200 cap).
Aggregate the trademark corpus with body filters — The SAME aggregate as get_trademark_insights, with the filters in the body. Read-only. Identical to REST POST /insights/trademarks/search. Every filter of list_trademarks is APPLIED with the same semantics (lists are OR). `q` counts the marks whose denomination contains every token of `q` (accent-insensitive: the search's exact lexical channel, without its 200 cap). NOT accepted — 400 validation_error — similarTo, similarToTrademark, allClasses, oppositionWindow, citedNorm, article, letter, face
Corpus freshness report — Per-source corpus freshness / staleness report, wrapped in the { data, dataAsOf? } envelope. Read-only. Identical to REST GET /system/freshness?envelope=true.
Recent sync-run history — Recent sync-run history (per source-run status + counts), newest first, wrapped in the ⭐ Fase 38: el sobre único { results, limit, next, hasMore, total?, meta }. Read-only.
Cobertura de ingesta por fecha de boletín — Qué días de boletín se han procesado y cuántos actos emitió cada uno, con la marca de feriado por fecha. Read-only. Identical to REST GET /system/coverage.
El horizonte de la vigilancia — Cuánto hacia atrás se puede preguntar por cambios, según la retención real de movement_log. Read-only. Identical to REST GET /system/vigilance-horizon.
Quién soy, qué alcances tengo y cuánta cuota me queda — El consumidor de la clave presentada: su identidad (org), sus alcances y su cuota mensual (límite, consumido, restante y segundos hasta el reinicio). Read-only. Identical to REST GET /system/me.
List parties — Find a party by fuzzy name or exact tax id and see how much of the register is theirs: the party's details plus its trademark count, heaviest first. Read-only. Identical to REST GET /parties.
⛔ It does NOT filter out parties with zero marks (`D-09`): a party with no marks today may hold them tomorrow, and why it is in the corpus is a datum. Pass `kind` (natural|legal|unknown) or `role` (holder|representative) to narrow; `taxId` is the exact Chilean RUT.
Each party carries `territory` — the Chi
Get one party — Fetch ONE party by its stable identifier. Read-only. Identical to REST GET /parties/{id}. An unknown identifier returns a structured not_found (mirroring REST's 404).
List the trademarks of one party — The marks of ONE party, by paper and validity. Read-only. Identical to REST GET /parties/{id}/trademarks.
⭐ The paper travels HERE — in the relation — not in the entity: `role` is holder|applicant|representative|opponent (holder/representative are the ownership roles; applicant/opponent are annotation roles and return nothing here), and `relation` is current|former|all (default current).
Chilean statutory holiday calendar — The holidays the corpus itself uses to count business days (opposition windows, appeal deadlines), so a caller can compute the same deadlines and audit ours. Read-only.
Each row declares whether it is 'regular' (derivable from a permanent rule) or 'excepcional' (an ad-hoc law or election decree, which no loader can reproduce), plus where the row came from.
COVERAGE IS FINITE: `coverage` reports the range actually seeded. A date outside it is NOT a business day by omission — it is unknown, so d
List the 45 Nice classes — The 45 Nice classification classes, served from code (not the database): the titles are INAPI's own classifier wording, transcribed 2026-09-14. Read-only. Identical to REST GET /nice-classes. `goodsAndServices` and `status` are per-MARK and are always null here.
List the legal norms cited by the corpus — The flat catalog of legal norms the corpus cites, each with its articles as data of the object. Read-only. Identical to REST GET /legal-norms. ⛔ There is no nested route per article: what is cited is FILTERED where it is cited (`citedNorm`/`article`/`letter` on annotations and trademark search).
Get one legal norm, with its articles — One legal norm by its identifier, with its cited articles as data of the object. Read-only. Identical to REST GET /legal-norms/{id}.
List the INAPI section codes — The enumerable catalog of INAPI section codes, with family, emitting sources, whether it carries parties, and confirmed equivalents. Read-only. Identical to REST GET /sections. ⛔ Where INAPI never named a code, the label is null — never an invented name.
Get one INAPI section, with its equivalents — One INAPI section by its code, with its confirmed equivalents. Read-only. Identical to REST GET /sections/{code}.
Explicar un código de sección de INAPI — Explica un código de sección de INAPI desde el repositorio de conocimiento. Si no hay leyenda, responde no_se_sabe — nunca una explicación plausible.
Create a watchlist — Create a watchlist under the caller's org, with an optional narrowing filter set and an optional https callback. Enforces the per-tenant caps (rejects watchlist_too_large) and validates the callback against SSRF. Returns the watchlist + its signing secret ONCE (never surfaced by any read). Identical to REST POST /watchlists. An optional idempotencyKey makes a retry safe: same key + same body replays the original result; same key + different body → idempotency_conflict.
List watchlists — List the caller's own watchlists (never another tenant's, never the signing secret). Identical to REST GET /watchlists.
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 33 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Obviouy require?
Obviouy may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.