Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory
Menu

Peru Sunat Ruc

MCP server · gateway.pipeworx.io · found in a public list · checked since 2026-11-01

Live, handshake completed · latest check

As JSON

Looks up Peru's SUNAT taxpayer register records by RUC number.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means

Placed in Company registry records: Look up official business register records by country: registration, status, officers, owners and filings.

https://gateway.pipeworx.io/peru-sunat-ruc/mcp MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person. See 1916 endpoints from pipeworx.io.

Our checks

An unpaid request weekly, from eastern North America

Last 1 checks, oldest to newest; room for 29 more

1 passed, 0 failed, 29 not run.

Passed, 30 daysshort history1 of 1 run
Checks missed0in 30 days
Response, latest429 mswhole handshake
Scheduleweeklyset by usage; rule below
Checked since2026-11-011 day
Freshnessfreshagainst its schedule

Checked weekly. Usually daily: Daily: 5 to 99 payers, and every new service until it has been probed 3 times. Checked weekly instead because its host has more services than our per-host limit lets us check at their usual intervals. One host: we send at most 2 checks to one host every five minutes (576 a day). When a host's services at the intervals above would need more than 288 checks a day (half of that, leaving room to catch up), every service on that host is checked one interval slower (hourly becomes daily, daily weekly, weekly monthly), and again if needed, until they fit. Each such service says so.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hourssince 2026-11-0110——————
7 dayssince 2026-11-0110——————
30 dayssince 2026-11-0110——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

ai_visibility_checkarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchclassify_rowcompany_factscompany_register_searchcompare_entitiesdeep_researchdiscover_toolsentity_profileforgetgenerate_llms_txtkalshi_weather_edgelist_subscriptionspe_rucpe_ruc_searchpipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadprediction_calibrationrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_within+6

Tools
46
This list since
2026-11-01
First listed to us
2026-11-01
List changes, 90 days
0

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
promptsresourcestools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

What it says about itself

Where it works
Perufrom its listing's description, read 2026-11-01

From the service's own text, put in short words by a small AI model and shown only where its own words support it (stated-facts/5): its claims, not checked by us. Anything not listed, it does not state. Definitions

Calls it declares

  • ask_pipeworx question* query q prompt text input ask message packs
  • ask_pipeworx_beta question* query q prompt text input ask message packs
  • ask_pipeworx_grounded question* query q prompt text input ask message prefer_tool
  • search_within text* query* limit
  • deep_research question* query q prompt text input ask message depth
  • discover_tools query* task q description search limit
  • resolve_entity type* value* country → type query resolved ids sources
  • compare_entities type* values*
  • subscribe type* params* delivery
  • unsubscribe id*
  • list_subscriptions include_inactive
  • recent_alerts type since limit unread_only mark_read

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Search and information / Companies and people / Company registry records (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-11-01. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:MIA		 Live, handshake completed HTTP 200 429 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_3c0e713948ba7977