Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

hardly

PYPI · HARDLY

Generic HAR analysis MCP server: index and query captures without burning tokens on raw files.

Available components

80 Trust /100

Last scanned (22 hours ago)

Scores higher than 80% of PyPI servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to b1tninja/hardly). View diagnostics → Pass
  • Clear OSI-approved license (MPL-2.0).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 11084 tokens (~136/item across 81 items; 71 tools + 10 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "hardly_send_catalog_verify" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 73 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +2
    • Stability: unverified → 0.13 ▲ functional
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 62

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Analysed pypi/hardly@1.0.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo b1tninja/hardly
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/b1tninja/hardly/.github/workflows/release.yml@refs/tags/v1.0.0
Rekor log index 3558925112
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:93338604fb2b1035a72732c25690371184435f36f124a59a97288783545c04eb

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 23 packages
Packages resolved 23
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 71 exposed · ~10,295 tokens

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 →

Tool Tokens
hardly_session_overview ~135

Headline COUNTS of a capture: requests per server, method and status, plus main_host (the app origin, not CDN/analytics). Run right after hardly_session_open; pass main_host as host= to later tools. Example: hardly_session_overview(session_id='S'). Distributions (content types, sizes, timing) are hardly_session_traffic_stats; findings with severity are hardly_session_report; a digest of a server-rendered site is hardly_session_site_brief.

NameTypeReqDescription
exclude_noiseboolean––
host–––
limit–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_plan_steps ~92

Suggest browser steps (goto/fill/click) from a session's story, ready for hardly_browser_run_steps. Heuristic: refine selectors with hardly_browser_inspect first. Nothing is run or written (hardly_write_export format=plan_steps saves them). Example: hardly_session_plan_steps(session_id='S').

NameTypeReqDescription
host–––
limit–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_redirect_history ~89

List the RECORDED 3xx redirect hops with matched follow-up entry ids; sends nothing. Use to understand login/canonicalisation redirects; the live twin that follows a URL is hardly_send_redirect_walk. Example: hardly_session_redirect_history(session_id='S').

NameTypeReqDescription
explainboolean––
host–––
limit–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_report ~199

One-pass evidence index (access, auth, stack, data, forms): FINDINGS with severity info|notice|blocker and the drill-down tool for each. Start here for any unfamiliar capture; detail='summary' is ~1 KB. Example: hardly_session_report(session_id='S', detail='summary'). Runs the existing detectors once and returns findings {section, kind, severity, label, entry_ids, names/shapes only, lookup}. detail: summary (counts per section + blockers) | standard | full (more findings + the drill-down tool per finding). ``categories`` restricts the sections (access, auth, stack, data, forms). Never returns secret values. explain=true adds canned prose. Writes nothing: hardly_write_export(format='report') saves it.

NameTypeReqDescription
categories–––
detailstring––
explainboolean––
host–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_site_brief ~117

One-shot DIGEST of a server-rendered site: journey (story), forms, routes, reused values, cookies and issues in a compact result. Run this first on a freshly opened session of an HTML portal, then drill down with the tools it names. Example: hardly_session_site_brief(session_id='S'). Findings with severities are hardly_session_report. Writes nothing: hardly_write_export (format='site_brief') saves it as Markdown.

NameTypeReqDescription
host–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_slow_requests ~91

List the slowest requests (time_ms) first. Use for performance questions; for the general traffic shape use hardly_session_traffic_stats. Example: hardly_session_slow_requests(session_id='S', min_elapsed_seconds=1).

NameTypeReqDescription
exclude_noiseboolean––
host–––
limit–––
min_elapsed_seconds–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_sql ~78

Run a read-only SELECT against the session's SQLite index. Escape hatch for questions no named tool answers; try those first. Example: hardly_session_sql(session_id='S', sql='select host, count(*) from entries group by host').

NameTypeReqDescription
limit–––
session_idstringyes–
sqlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_story ~139

Annotated user-journey NARRATIVE: the session stitched into steps (role, forms, labels, fields) with duplicates collapsed. Prefer it over the plain list hardly_session_timeline when reversing portals or building a client. Example: hardly_session_story(session_id='S', host='app.example.com'). It is the input to hardly_client_build. include_related=true adds non-noise traffic from sibling hosts on the same apex so SPA captures tell a full story.

NameTypeReqDescription
exclude_noiseboolean––
host–––
include_relatedboolean––
limit–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_timeline ~101

Plain ordered LIST of requests in time order for a host, optionally from a path_prefix; no annotation. Raw timeline for login/MFA sequences; hardly_session_story is the condensed narrative. Example: hardly_session_timeline(session_id='S', path_prefix='/login').

NameTypeReqDescription
exclude_noiseboolean––
host–––
limit–––
offset–––
path_prefix–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_trace_value ~117

Trace a field name or exact value across a capture: where it first appears and where it is reused. With neither name nor value, list every dynamic value (CSRF, ViewState, session cookies, tokens) reused from earlier responses. Example: hardly_session_trace_value(session_id='S', name='csrf_token'). Values are never echoed back, only entry ids, location and shape.

NameTypeReqDescription
host–––
limit–––
name–––
session_idstringyes–
value–––
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_session_traffic_stats ~142

DISTRIBUTIONS of a capture: MIME mix, status classes, body sizes, initiator types, timing and payload_kinds. Each has sample entry_ids. Example: hardly_session_traffic_stats(session_id='S', host='app.example.com'). Counts per server/method/status are hardly_session_overview; slow requests hardly_session_slow_requests; repeated calls hardly_session_duplicates. ``kind`` filters the payload_kinds list; ``limit`` caps it (default 80).

NameTypeReqDescription
exclude_noiseboolean––
host–––
kind–––
limit–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_spec_contract_check ~85

Compare a capture with a previously written OpenAPI file and report drift (new/removed endpoints, status, field, parameter, auth changes). Offline; removed means not observed. Example: hardly_spec_contract_check(session_id='S', spec_path='/data/api.yaml').

NameTypeReqDescription
host–––
session_idstringyes–
spec_pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_tech_stack ~138

Fingerprint web frameworks, CMS, GIS stacks, UI toolkits and data-grid widgets from header/cookie names, paths and body previews. Absent technology gives count 0. Example: hardly_tech_stack(session_id='S', explain=true). explain=true adds SDK implications. Data-grid frameworks, JSON envelope conventions (OData, JSON:API, HAL, Relay) and paging/sort styles are under ``data_grids``. For CDN/WAF products use hardly_gate_bot_protection.

NameTypeReqDescription
explainboolean––
host–––
limit–––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_write_catalog_record ~223

Writes a file: add or update one target in a catalog file in place (atomic, no network). URLs are redacted and validated. create=true makes the file if missing. Example: hardly_write_catalog_record(catalog_path='/data/targets.json', target={'id':'t1','endpoints':[{'role':'api','url':'https://example.com/api'}]}, create=true). Writes only inside the working directory, the OS temp dir or HARDLY_WRITE_DIRS (path_not_allowed). Only that one target changes (there is no overwrite flag; merge=false replaces the target). ``target`` is {id, name, tags[], groups{}, endpoints:[{role, url, kind?, status?, gate_classes?, stack?, notes?, capture?:{recipe_ref, har_ref}}]}. merge=true unions tags, overlays groups and merges endpoints by (role, url); merge=false replaces the target.

NameTypeReqDescription
catalog_pathstringyes–
createboolean––
mergeboolean––
targetobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_write_export ~348

Writes a file: export the session as format openapi, postman, api_markdown, site_brief, report, client_python or plan_steps to output_path. Secrets are redacted or placeholders; refuses to overwrite unless overwrite=true. Example: hardly_write_export(session_id='S', format='openapi', output_path='/tmp/api.yaml', host='api.example.com'). Writes only inside the working directory, the OS temp dir or HARDLY_WRITE_DIRS (path_not_allowed). openapi: OpenAPI 3 (JSON or YAML by file extension; input to hardly_spec_contract_check). postman: Collection v2.1 with {{placeholders}} (``title`` names it). api_markdown: API.md of the endpoints (``max_endpoints``, default 200). site_brief: the hardly_session_site_brief digest as Markdown. report: the hardly_session_report findings (``detail`` summary|standard|full, ``categories``; .json path = JSON, else Markdown; a directory gets <har>.report.md). client_python: the starter urllib client of hardly_client_build (``entry_ids``, ``class_name``). plan_steps: the JSON steps of hardly_session_plan_steps (``limit``).

NameTypeReqDescription
categories–––
class_name–––
detailstring––
entry_ids–––
exclude_noiseboolean––
formatstringyes–
host–––
limit–––
max_endpoints–––
output_pathstringyes–
overwriteboolean––
session_idstringyes–
title–––
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_write_har_merged ~126

Writes a file: merge several HARs into output_path, prefixing page ids and dropping exact duplicates (dedupe=true). Needs overwrite=true to replace. Example: hardly_write_har_merged(har_paths=['/data/a.har','/data/b.har'], output_path='/data/all.har'). Writes only inside the working directory, the OS temp dir or HARDLY_WRITE_DIRS (path_not_allowed).

NameTypeReqDescription
dedupeboolean––
har_pathsarrayyes–
output_pathstringyes–
overwriteboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_write_har_pruned ~142

Writes a file: a pruned copy of a HAR (drop hosts, mime globs, known noise); never in place, refuses an existing output_path unless overwrite=true. Example: hardly_write_har_pruned(har_path='/data/a.har', output_path='/data/a.small.har', drop_noise=true). Writes only inside the working directory, the OS temp dir or HARDLY_WRITE_DIRS (path_not_allowed).

NameTypeReqDescription
drop_hosts–––
drop_mime_types–––
drop_noiseboolean––
har_pathstringyes–
output_pathstringyes–
overwriteboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_write_har_scrubbed ~129

Writes a file: a scrubbed copy of a HAR with secret values, cookies and auth headers replaced by ***REDACTED*** (structure and shapes kept). Never in place; needs overwrite=true to replace. Example: hardly_write_har_scrubbed(har_path='/data/a.har', output_path='/data/a.scrubbed.har'). Writes only inside the working directory, the OS temp dir or HARDLY_WRITE_DIRS (path_not_allowed).

NameTypeReqDescription
har_pathstringyes–
output_pathstringyes–
overwriteboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_write_har_split ~138

Writes files: split a HAR into one file per host (by='host') or per page (by='page') inside output_dir, streaming. Example: hardly_write_har_split(har_path='/data/a.har', output_dir='/data/parts'). Writes only inside the working directory, the OS temp dir or HARDLY_WRITE_DIRS (path_not_allowed). Use for huge captures, then hardly_session_open each part. Refuses to overwrite existing parts unless overwrite=true.

NameTypeReqDescription
bystring––
har_pathstringyes–
output_dirstringyes–
overwriteboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_write_screenshot ~112

Writes a file: save a PNG screenshot of the running browser tab to output_path. Use to show a person or inspect a wall; refuses to overwrite unless overwrite=true. Example: hardly_write_screenshot(output_path='/tmp/page.png', full_page=true). Writes only inside the working directory, the OS temp dir or HARDLY_WRITE_DIRS (path_not_allowed).

NameTypeReqDescription
capture_id–––
full_pageboolean––
output_pathstringyes–
overwriteboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

hardly_write_session_copy ~153

Writes a file: save a copy of the session's source HAR (format='har') or its SQLite index (format='index') to output_path. Never in place; refuses to overwrite unless overwrite=true. Example: hardly_write_session_copy(session_id='S', output_path='/data/keep.har'). Writes only inside the working directory, the OS temp dir or HARDLY_WRITE_DIRS (path_not_allowed). An ephemeral capture's HAR is already deleted (code har_ephemeral_gone): save the index instead, or capture again with har_output_path.

NameTypeReqDescription
formatstring––
output_pathstringyes–
overwriteboolean––
session_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the hardly MCP server?

hardly runs locally as a PyPI package, launched with uvx hardly. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · hardly

# add to Claude Code
claude mcp add b1tninja-hardly -- uvx hardly
Common questions

What is the hardly MCP server?

hardly is an MCP server listed in the public MCP registry as io.github.b1tninja/hardly. Generic HAR analysis MCP server: index and query captures without burning tokens on raw files. This page covers its PyPI package (hardly).

Is the hardly MCP server safe to use?

hardly scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 hardly MCP server expose?

hardly exposes 71 tools: hardly_server_status, hardly_guide_help, hardly_guide_mode, hardly_guide_task_plan, hardly_session_open, and 66 more. Their descriptions and schemas cost roughly 10,295 tokens of context every time the server is loaded.

Is the hardly MCP server still maintained?

hardly is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the hardly MCP server under?

hardly declares the MPL-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.