16 tools from the Hyperplexity MCP Server, categorised by risk level.
View the Hyperplexity policy →get_balance Return the current account credit balance in USD. get_conversation Poll a conversation for new messages or a status change.
Key statuses:
processing → poll again in ~15s
user_re... get_job_messages Fetch live progress messages for a running job.
Pass since_seq from the last message to receive only new messages.
get_job_status One-shot job status check. Prefer wait_for_job for tracking long-running jobs.
Use this for quick status inspections or as a fallback when... get_results Fetch the final validated/enriched results for a completed job.
job_id: the session_id value — "job_id" and "session_id" are the same stri... get_usage Return API usage history. Dates in YYYY-MM-DD format. approve_validation Approve a preview and start full validation processing.
job_id: the session_id value — "job_id" and "session_id" are the same string.
... 2/5 send_conversation_reply Send a user reply in an ongoing conversation (interview or table-maker).
After sending, poll get_conversation for the AI's next response.
... 2/5 update_table Re-run validation on a previously processed table (update in place).
source_version can pin a specific prior result version; omit for late... 2/5 upload_file Upload a local file to Hyperplexity.
Compound tool: reads the file, gets a presigned S3 URL, PUTs the bytes
(without auth headers ... 3/5 start_reference_check Submit a reference-check job to fact-check text or a document.
For inline text:
start_reference_check(text="The claims to fact-c... 3/5 start_table_maker Start a Table Maker conversation to generate a research table.
Describe the table you want in natural language, e.g.:
'Create a ta... 3/5 start_table_validation Confirm the upload and detect matching prior configs.
Call this immediately after upload_file. Returns config_matches with
match_s... 4/5 wait_for_conversation Wait for a conversation turn to complete, emitting live synthetic progress.
Preferred over manually polling get_conversation. Since conver... 3/5 wait_for_job Wait for a job to reach a terminal state, emitting live MCP progress notifications.
Preferred over manually looping get_job_status. The MC... 4/5 The Hyperplexity MCP server exposes 16 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Hyperplexity server.
Hyperplexity tools are categorised as Read (6), Write (4), Destructive (1), Execute (5). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept