Skip to content

Lingshu Solver MCP server

io.github.genesis-plan/lingshu-solvergenesis-planstreamable-httpv1.0.23Scanned

Deterministic MCP solver for real equation systems (<=6 vars), Krawczyk-certified.

6 tools: 1 do something that can't be undone and 5 change things.

Tools: 0 delete, 1 irreversible, 5 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 2 findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

6 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Lingshu Solver MCP server can do

The Lingshu Solver MCP server is published by the GitHub account genesis-plan. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (pay) and create or change data (5 tools: solve, give_feedback, poly_roots, verify and 1 more), but cannot delete data. None of its tools only reads.

1 tool can send data out of your system (pay).

The fixed checks matched 2 findings (long-description and credentials-mention). Each one comes with the text it matched.

Last scanned Oct 21, 2026, version 1.0.23.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Can't be undone 1Claude Code: ask
  • payOptional voluntary-support only.Can send data out1 finding

    Why it is in this group

    • The name "pay" says "pay": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.channel): what the tool writes goes there.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...today (metering off) (metering off: no credential required, no call limit, no per-call ch..."

      What this check looks for
    Description, as the server wrote it
    Optional voluntary-support only. The hosted endpoint is no per-call charge today (metering off) (metering off: no credential required, no call limit, no per-call charge), so no payment is needed at all. This tool records a support contribution of any amount: the channel is a corporate static collection code (UnionPay aggregate QR) settling into a corporate bank account, and no payment-platform merchant API is used. AFTER PAYING: nothing to do — there is no self-crediting step and no waiting for reconciliation; the operator reconciles against the corporate bank statement, and any positive amount counts as support, not a bill. If the server has no payment method configured the order is still created but payIntent.payTo is null; in that case just keep calling the endpoint with no credential at all.
Changes things 5Claude Code: ask
  • geometryDeterministic 1D/2D/3D geometry: distances, intersections, areas, volumes, angles, convex hull, point-in-polygon, rotations.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description is 2,860 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: ".../ coplanar / coincident), do NOT invent a value — report the degeneracy instead."

      What this check looks for
    Description, as the server wrote it
    Deterministic 1D/2D/3D geometry: distances, intersections, areas, volumes, angles, convex hull, point-in-polygon, rotations. Closed-form (not iterative), exact up to floating-point rounding, identical output for identical input. Use it instead of doing geometry yourself. Pass {op, ...args} with op one of: 1D: dist1,midpoint1,divide_point,divide_ratio,harmonic_conjugate,interval_length,interval_midpoint,interval_intersect,interval_union,interval_hull,interval_overlap_length,interval_contains,point_between | 2D: dist2,midpoint2,lerp2,line_from_points,point_line_distance,point_segment_distance,project_point_line,line_intersect,line_intersect_points,segment_intersect,segment_length,angle_3points,angle_vectors,line_angle,triangle_area,triangle_centroid,triangle_incenter,polygon_area,polygon_perimeter,polygon_centroid,point_in_polygon,convex_hull,polygon_is_convex,circle_from_3points,point_circle_position,circle_line_intersect,circle_circle_intersect,circle_measure,sector_area,rotate_point,reflect_point_line,scale_point,parallel_through,perpendicular_through,triangle_circumcenter,triangle_orthocenter,triangle_excenters,triangle_five_centers,euler_line,triangle_nine_point_circle,triangle_euler_inequality,triangle_medians,triangle_altitudes,triangle_bisector_lengths,cevian_concurrent,menelaus_collinear,power_of_point,radical_axis,polar_of_point,pole_of_line,ptolemy,miquel_point,napoleon_triangles,pick_theorem,cocircular_check,minimum_enclosing_circle,circumcircle | 3D: dist3,midpoint3,lerp3,plane_from_3points,point_plane_distance,project_point_plane,reflect_point_plane,coplanar,point_line_distance3,project_point_line3,line_plane_intersect,line_line_relation,plane_plane_intersect,tetra_volume,polygon_area3,face_normal,mesh_volume,sphere_from_4points,sphere_line_intersect,sphere_plane_intersect,sphere_measure,angle_vectors3,angle_line_plane,angle_plane_plane,rotate_axis,cross3,triple_product,tetrahedron_geometry,monge_point | any: distance,midpoint,lerp,norm,normalize,dot,cross,project,reject,translate,centroid,bbox,diameter,stewart_theorem,law_of_cosines,law_of_cosines_sas,law_of_sines,solve_triangle,heron_area,brahmagupta,golden_ratio,regular_polygon,regular_tetrahedron,newton_polytope,tropical_degree_bound,tropical_system_bound,regular_subdivision,bernstein_bound,tropical_bezout_bound,sphere_equation,polynomial_equation. The remaining args are passed flat and depend on op (p, q, a, b, c, d, r, poly, pts, angle, lambda, center, axis, segment, a1,b1,c1,a2,b2,c2, ...). Send an unknown op to receive the full catalog with every signature. READ trust.trustLevel: exact = safe to use directly; definitely_none = computed proof that there is NO intersection, safe to state as a conclusion; degenerate = the INPUT is degenerate (parallel / collinear / coplanar / coincident), do NOT invent a value — report the degeneracy instead.
  • give_feedbackReport a problem to the operator when solve hits a dead end, returns an error, or produces something you believe is wrong.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Report a problem to the operator when solve hits a dead end, returns an error, or produces something you believe is wrong. The text is written to a local log only and is never transmitted anywhere else.
  • poly_rootsAll real roots of a polynomial, each individually Krawczyk-certified with a strict error box.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    All real roots of a polynomial, each individually Krawczyk-certified with a strict error box. Coefficients are highest degree first: [1,-2,-5,6] means x^3-2x^2-5x+6. Use it instead of letting a language model estimate roots. Complex roots are not returned (real only).
  • solveDeterministic (non-LLM) solver for systems of real equations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Deterministic (non-LLM) solver for systems of real equations. Use it instead of computing the math yourself whenever a wrong number has a cost. Same input always returns the identical result — no hallucination, no randomness, so caching and retries are safe. Supports algebraic equations and common transcendentals (sin/cos/tan/log/exp/sqrt/abs), max 6 variables, no initial guess needed. READ THE trust BLOCK: it tells you, per result, whether the value is safe to use directly or must be verified first. Pass domain explicitly for exp/sin or large ranges, else truncated may be true. Not for symbolic derivation, initial-value ODEs, or integer constraints. Optional: pass honorPaid:true to declare personal or evaluation use — then it is served free with no key, no balance and no deduction; payment is voluntary and never enforced.
  • verifyCheck whether a claimed answer is actually correct — call this on any number you computed yourself before passing it downstream.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check whether a claimed answer is actually correct — call this on any number you computed yourself before passing it downstream. verdict=verified means it is a certified real root; verdict=refuted_or_unverified means it is NOT, and nearestCertifiedRoot then carries the correct value so you can self-correct in the same turn. Deterministic and reproducible.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:05 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
525
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 525.

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 525
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2024-11-05 to none

Findings

Matches of fixed checks, with the text they matched.

2 info
  • The description is 2,860 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: ".../ coplanar / coincident), do NOT invent a value — report the degeneracy instead."

    What this check looks for
  • Infopay

    The description mentions "credential".

    Matched text

    description: "...today (metering off) (metering off: no credential required, no call limit, no per-call ch..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 525; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 6 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 525
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2024-11-05 to none

Install

Pinned to version 1.0.23. Values in angle brackets are yours to fill in.

claude mcp add --transport http lingshu-solver https://hongchenlingjing.com/mcp
claude mcp add --transport http lingshu-solver https://hongchenlingjing.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__lingshu-solver__solve",
      "mcp__lingshu-solver__give_feedback",
      "mcp__lingshu-solver__poly_roots",
      "mcp__lingshu-solver__verify",
      "mcp__lingshu-solver__geometry",
      "mcp__lingshu-solver__pay"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lingshu-solver. Review it before you use it.

Capability tags behind 1 rule
  • mcp__lingshu-solver__pay outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.genesis-plan/lingshu-solver/verify?hash=6b58ea2dcd3014f4de27a29a7fb97ecdc61b22f16c838b694f06d23d4aa54c07" | jq -e '.changed == false'

Pinned hash 6b58ea2dcd30, from Oct 21, 2026, 19:22 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.genesis-plan/lingshu-solver/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.genesis-plan/lingshu-solver
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.genesis-plan/lingshu-solver.svg)](https://radar.anlyon.com/servers/io.github.genesis-plan/lingshu-solver)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.

Lingshu Solver MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Lingshu Solver MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 6 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Lingshu Solver MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Lingshu Solver MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: pay.

What tools does the Lingshu Solver MCP server have?

6 tools: 1 irreversible, 5 write. pay, solve, give_feedback, poly_roots, verify and geometry.

Does the Lingshu Solver MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Lingshu Solver MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): pay.

Has the Lingshu Solver MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.