MLP Tax Computation Engine MCP server
ai.lucasandersen/mlp-taxlucasandersen.aistreamable-httpv1.0.0Scanned
Deterministic MLP tax engine with IRS citations. 6 tools: basis, §751, estate, projections.
6 tools: 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MLP Tax Computation Engine MCP server can do
The MLP Tax Computation Engine MCP server is published by lucasandersen.ai, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: mlp_projection, mlp_estate_planning, k1_basis_compute and k1_basis_multi_year), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.0.
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
Changes things 4Claude Code: ask
k1_basis_computeComputes adjusted partner basis from a single year of Schedule K-1 data using the IRS Partner's Basis Worksheet methodology (Lines 1-14), per IRC §705, §722, §731(a)(1), §733, §752…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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Computes adjusted partner basis from a single year of Schedule K-1 data using the IRS Partner's Basis Worksheet methodology (Lines 1-14), per IRC §705, §722, §731(a)(1), §733, §752, §704(d) and §199A. Returns the ending adjusted basis, every worksheet line value, any §731 gain triggered when distributions exceed basis, and §704(d) suspended losses carried forward. Use when: User holds direct MLP units (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN, or similar publicly traded midstream partnerships) and has structured K-1 box values for one tax year — Box 1 ordinary income, Box 19A cash distributions, Item K liability change, optionally Box 5 interest income, Box 11 §179 deduction, Box 13W §199A QBI amount. Single tax year, single lot. Don't use for: 1099-DIV ETFs (AMLP, MLPX, AMZA): this tool does not model them. Multi-year basis carryforward across consecutive K-1s — use k1_basis_multi_year. General partnership interests outside publicly traded MLPs (different §1402 self-employment treatment). Limitations: Single tax year only — for multi-year basis tracking with §731 gain detection across years, use k1_basis_multi_year. Single-lot only — for multi-lot allocation and optimal sell ordering, see lucasandersen.ai. Federal-level only — does not include state basis adjustments. Full multi-year basis reconstruction with a CPA-ready workpaper is available at https://lucasandersen.ai/private-partnership-k1-basis?src=mcp&tool=k1_basis_compute&surface=description. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology.
Annotations the server declares
- title: K-1 Single-Year Basis Worksheet
- readOnlyHint: true
- idempotentHint: true
k1_basis_multi_yearComputes a running adjusted partner basis across multiple years of Schedule K-1 data, per IRC §705, §731(a)(1), §751(a), §752 and §704(d), with §1014(a) cited for the successor's b…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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Computes a running adjusted partner basis across multiple years of Schedule K-1 data, per IRC §705, §731(a)(1), §751(a), §752 and §704(d), with §1014(a) cited for the successor's basis at death (R-1014-PTP-STEP-UP). Returns year-by-year basis trajectory, accumulated §751 recapture estimate and projected zero-basis year. Use when: User holds a direct MLP position (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN) across multiple consecutive tax years, has K-1s for those years, and wants to track adjusted basis year over year, or identify the zero-basis year. Don't use for: Single-year basis worksheet from one K-1 — use k1_basis_compute. Long-horizon forward projection from default assumptions when no actual K-1s are in hand — use mlp_projection. 1099-DIV ETFs (AMLP, MLPX, AMZA): this tool does not model them. Multi-position portfolio basis tracking — this tool handles one position per call. Limitations: Single position, single lot — for multi-lot or multi-position basis tracking with optimal sell ordering, see lucasandersen.ai. Federal-level only — does not include state-level basis adjustments. Accumulated §751 recapture is estimated across years; actual depends on the partnership's hot-asset disposition schedule and any year-specific §751(b) events. Full multi-year basis reconstruction with a CPA-ready workpaper is available at https://lucasandersen.ai/private-partnership-k1-basis?src=mcp&tool=k1_basis_multi_year&surface=description. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology.
Annotations the server declares
- title: Multi-Year K-1 Basis & Broker-Gap Tracker
- readOnlyHint: true
- idempotentHint: true
mlp_estate_planningComputes an estate view for one or more direct MLP positions with no sale by the holder, per IRC §705, §731 and §751(a), with §1014(a) cited for the successor's basis at death (R-1…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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 2,523 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...s in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology."
Description, as the server wrote it Computes an estate view for one or more direct MLP positions with no sale by the holder, per IRC §705, §731 and §751(a), with §1014(a) cited for the successor's basis at death (R-1014-PTP-STEP-UP). Returns the projected market value, the tax a sale by the holder at that value would carry and its §751 amount (each position priced as if sold alone; not a measure of tax saved or avoided at death; the successor's tax is not computed), the projected value less adjusted basis, a per-beneficiary split, and the difference between holding with no sale and selling today. If the units pass at death, the successor's basis is generally the fair market value at that date (or the §2032 alternate value where the executor elects), increased by the successor's share of partnership liabilities on that date and reduced to the extent the value is attributable to income in respect of a decedent, outside basis only; the partnership's basis in its property, from which the §751 amount on a later sale is figured, is adjusted only with a §754 election or a substantial built-in loss immediately after the transfer (R-1014-PTP-STEP-UP). The community-property option is withdrawn: a call with community_property true is rejected. Use when: User has one or more direct MLP positions (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN) and wants the projected value and, if the units pass at death, the successor's basis proxy (the projected value before the liability-share and IRD adjustments) across a portfolio, a comparison of holding with no sale against selling now, or per-beneficiary values across several beneficiaries. Don't use for: Units held in a trust, IDGT, FLP or charitable structure (this tool models direct holdings only). Single-position long-horizon tax projection — use mlp_projection. Single-position sell-now-versus-hold break-even — use mlp_sell_vs_hold. 1099-DIV ETFs (AMLP, MLPX, AMZA): this tool does not model them. Limitations: Direct unit holdings only; does not model trust, IDGT, FLP or charitable structures. Does not compute estate tax, federal or state. The §751 amount is estimated from default ROC assumptions; the exact figure depends on the partnership's actual hot-asset disposition schedule. A year-by-year basis workpaper for this position is available at https://lucasandersen.ai/tax/k1-basis-tracker?src=mcp&tool=mlp_estate_planning&surface=description. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology.
Annotations the server declares
- title: MLP Estate Planning: Basis at Death Under §1014
- readOnlyHint: true
- idempotentHint: true
mlp_projectionComputes a multi-year tax projection for a publicly traded MLP position, applying the IRS Partner's Basis Worksheet methodology per IRC §705, §731(a), §733, §751, §752 and §199A.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Computes a multi-year tax projection for a publicly traded MLP position, applying the IRS Partner's Basis Worksheet methodology per IRC §705, §731(a), §733, §751, §752 and §199A. Returns year-by-year basis erosion, §751 accumulation, annual federal tax, terminal FMV (the projected market value), the tax on a sale by the holder at that value (not a measure of tax saved or avoided at death; the successor's tax is not computed), and the break-even sell price. Use when: User holds direct units of a midstream MLP (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN) and wants to model long-term tax outcomes — when basis reaches zero, total tax paid over the hold horizon, the tax a sale at the projected value would carry, or the unit price at which selling now matches holding with no sale. Single position, single lot. Don't use for: 1099-DIV ETFs (AMLP, MLPX, AMZA): this tool does not model them. Multi-position estate analysis — use mlp_estate_planning. Computing basis from actual K-1 data the user has in hand — use k1_basis_compute (single year) or k1_basis_multi_year. Limitations: Single position, single lot — for multi-position portfolios and per-lot optimal sell ordering, see lucasandersen.ai. Federal-level only — does not include state-level basis adjustments or state estate tax. §751 recapture is estimated from default ROC assumptions; actual recapture depends on the partnership's hot-asset disposition schedule. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology.
Annotations the server declares
- title: MLP Multi-Year Tax Projection
- readOnlyHint: true
- idempotentHint: true
Only reads 2Show 2 read-only tools
mlp_infoReturns reference data for a supported MLP ticker — current cash distribution per unit, distribution growth CAGR, default return-of-capital percentage, distribution coverage ratio,…No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Returns reference data for a supported MLP ticker — current cash distribution per unit, distribution growth CAGR, default return-of-capital percentage, distribution coverage ratio, K-1 entity count, operating-state count, and last-verified date. Use when: User wants to look up baseline characteristics of an MLP before modeling — e.g., comparing distribution coverage across partnerships, checking how many K-1 entities a holding generates for tax-prep complexity, or seeing the operating-state count for state-tax filing-burden estimation. Don't use for: Tax computation. Use mlp_projection (long-horizon modeling), mlp_estate_planning (estate analysis), mlp_sell_vs_hold (break-even sell price), or k1_basis_compute / k1_basis_multi_year (computing basis from actual K-1 data). Note: This tool returns reference data only — no IRC citations apply, no methodology disclosure attached. For computation, use the modeling tools above. Maintained by Lucas Andersen, MS Finance.
Annotations the server declares
- title: MLP Reference Data Lookup
- readOnlyHint: true
- idempotentHint: true
mlp_sell_vs_holdCompares selling an MLP position today (the §751(a) ordinary amount plus capital gain on the rest, R-751-BIFURCATION) against holding it with no sale by the holder through the proj…1 finding
Why it is in this group
- The description's first verb is "compare": a word for reading.
Findings
- Info
The description is 2,668 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...s in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology."
Description, as the server wrote it Compares selling an MLP position today (the §751(a) ordinary amount plus capital gain on the rest, R-751-BIFURCATION) against holding it with no sale by the holder through the projection horizon, per IRC §199A (qualified PTP income, including §751(a) gain attributable to the PTP's trades or businesses; R-199A-PTP-751-PAL) and §1411. Returns the break-even sell price: the unit price above which selling today produces more in this projection than holding with no sale (holding counts the projected value with no tax deducted, plus net distributions). It also returns the tax a sale by the holder at the projected value would carry, which is not a measure of tax saved or avoided at death; the successor's tax is not computed. If the units pass at death, the successor's basis is generally the fair market value at that date (or the §2032 alternate value where the executor elects), increased by the successor's share of partnership liabilities on that date and reduced to the extent the value is attributable to income in respect of a decedent, outside basis only; the partnership's basis in its property, from which the §751 amount on a later sale is figured, is adjusted only with a §754 election or a substantial built-in loss immediately after the transfer (R-1014-PTP-STEP-UP). Use when: User holds a direct MLP position (EPD, ET, MPLX, WES, PAA, NRP, USAC, SUN), is approaching a sell decision, and wants a single break-even threshold to compare against the current market price. Useful for time-sensitive sell decisions, retirement-distribution planning, or comparing an unsolicited tender offer with continuing to hold. Don't use for: Multi-position portfolio sell-ordering — this tool models a single position. For estate-planning analysis across multiple positions and beneficiaries, use mlp_estate_planning. For long-horizon basis-erosion modeling without a sell decision in view, use mlp_projection. 1099-DIV ETFs (AMLP, MLPX, AMZA): this tool does not model them. Limitations: Single position, single lot — for portfolio-wide optimal sell ordering across multiple positions and lots, see lucasandersen.ai. Break-even price assumes the supplied tax bracket persists through the hold horizon. §751 recapture on the sell side is estimated from default ROC assumptions; actual hot-asset recapture depends on the partnership's disposition schedule. A year-by-year basis workpaper for this position is available at https://lucasandersen.ai/tax/k1-basis-tracker?src=mcp&tool=mlp_sell_vs_hold&surface=description. Maintained by Lucas Andersen, MS Finance, with direct positions in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology.
Annotations the server declares
- title: MLP Sell-Now vs Hold Break-Even
- readOnlyHint: true
- idempotentHint: true
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 or outbound.
- 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 out0
- 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.
Looked at Nov 20, 2026, 18:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2024-11-05
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.lucasandersen.ai/mcp: tools/list returned 6 tools to an anonymous client, including mlp_projection (write), mlp_estate_planning (write), k1_basis_compute (write), k1_basis_multi_year (write)
Findings
Matches of fixed checks, with the text they matched.
The description is 2,523 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...s in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology."
- Infomlp_sell_vs_hold
The description is 2,668 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...s in major midstream MLPs. Methodology auditable at lucasandersen.ai/methodology."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http mlp-tax https://api.lucasandersen.ai/mcpclaude mcp add --transport http mlp-tax https://api.lucasandersen.ai/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__mlp-tax__mlp_sell_vs_hold",
"mcp__mlp-tax__mlp_info"
],
"ask": [
"mcp__mlp-tax__mlp_projection",
"mcp__mlp-tax__mlp_estate_planning",
"mcp__mlp-tax__k1_basis_compute",
"mcp__mlp-tax__k1_basis_multi_year"
],
"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 mlp-tax. Review it before you use it.
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/ai.lucasandersen/mlp-tax/verify?hash=fd0c3631845b8124e905945d5b440a58bb5172d199f0f95302679fc1e570436f" | jq -e '.changed == false'Pinned hash fd0c3631845b, from Nov 10, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.lucasandersen/mlp-tax/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.lucasandersen/mlp-tax)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:42 UTC.
MLP Tax Computation Engine MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MLP Tax Computation Engine MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 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 MLP Tax Computation Engine MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MLP Tax Computation Engine MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the MLP Tax Computation Engine MCP server have?
- 6 tools: 4 write, 2 read. mlp_projection, mlp_estate_planning, k1_basis_compute, k1_basis_multi_year, mlp_sell_vs_hold and mlp_info.
Does the MLP Tax Computation Engine MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MLP Tax Computation Engine MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MLP Tax Computation Engine MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.