@viberaven/mcp 1.7.1 → 1.7.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE CHANGED
@@ -1,21 +1,21 @@
1
- MIT License
2
-
3
- Copyright (c) 2026 VibeRaven
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in all
13
- copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
- SOFTWARE.
1
+ MIT License
2
+
3
+ Copyright (c) 2026 VibeRaven
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
@@ -554,7 +554,7 @@ function mcpVersion() {
554
554
  } catch {
555
555
  }
556
556
  }
557
- found ??= true ? "1.7.1" : void 0;
557
+ found ??= true ? "1.7.2" : void 0;
558
558
  if (!found || !PLAIN_VERSION.test(found)) {
559
559
  throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
560
560
  }
package/dist/server.js CHANGED
@@ -573,6 +573,321 @@ var registry_generated_default = {
573
573
  }
574
574
  };
575
575
 
576
+ // ../providers/recent-changes.generated.mjs
577
+ var recent_changes_generated_default = {
578
+ "hash": "d2aaaaf9089270914954d2a8fd7b4fa3933c8525111162650feeb7bf726c67dc",
579
+ "pack": {
580
+ "schemaVersion": 1,
581
+ "packVersion": "1.0.0",
582
+ "reviewedAt": "2026-10-30",
583
+ "dateConvention": "effective = provider-stated date; announced = publication/release date; verified = checked date only, not rollout.",
584
+ "limits": [
585
+ "Guidance only; repository and live provider state remain not_checked.",
586
+ "Static, reviewed official sources can change. A matching entry is a candidate explanation, not a diagnosis or evidence that a fix worked.",
587
+ "No provider connection, account, credential, runtime file read, network request, deployment or data change is performed."
588
+ ],
589
+ "correctionsAndConflicts": [
590
+ "Lovable current official dates Oct 23 retirement/Dec 1 deletion replace seeded Oct5/Nov 4. Affected built-in-backend projects only.",
591
+ "Vercel current docs list 26.x default; 24.x remains supported but is not the current default claim.",
592
+ "Railway IaC migration doc says --apply clears settings, but newer Oct 16 changelog explicitly requires separate cutover. Current CLI help must be inspected before execution.",
593
+ "Railway announcement has2026-08-21 visible publish date despite Aug 20 URL; avoid inventing Aug 20 announced date.",
594
+ "Clerk production-instance setup is evergreen verified Oct 30, not an Oct 30 provider change. Related secret masking is dated Oct 19.",
595
+ "Supabase legacy-key end 2026 deprecation is not an exact shutdown day; no mandatory day invented."
596
+ ],
597
+ "sources": [
598
+ {
599
+ "id": "supabase-grants-announcement",
600
+ "url": "https://supabase.com/changelog/45329-breaking-change-tables-not-exposed-to-data-and-graphql-api-automatically",
601
+ "notes": "Dated April 28, 2026. Announces October 30 application to existing projects; newly created public tables need explicit grants. Existing table grants persist; direct Postgres users unaffected. Official example uses code 42501 and permission denied for table your_table."
602
+ },
603
+ {
604
+ "id": "supabase-api-security",
605
+ "url": "https://supabase.com/docs/guides/api/securing-your-api",
606
+ "notes": "Grants determine object/role access; RLS controls rows. Configure both for API-exposed tables. Does not prove hosted project rollout or actual grants."
607
+ },
608
+ {
609
+ "id": "vercel-node20-announcement",
610
+ "url": "https://vercel.com/changelog/node-js-20-is-being-deprecated",
611
+ "notes": "Published July 14, 2026. October 1 deprecation for Builds/Functions affects new deployments, not existing invocations. Official upgrade example sets engines.node to 24.x, matches local/CI and reruns build/tests."
612
+ },
613
+ {
614
+ "id": "vercel-node-versions",
615
+ "url": "https://vercel.com/docs/functions/runtimes/node-js/node-js-versions",
616
+ "notes": "Current docs list 26.x default and 24.x/22.x supported. package.json engines.node overrides Project Settings. Do not repeat seed's 24.x default claim."
617
+ },
618
+ {
619
+ "id": "vercel-node-error-source",
620
+ "url": "https://raw.githubusercontent.com/vercel/vercel/main/packages/build-utils/src/fs/node-version.ts",
621
+ "notes": "Official mutable main source lists20.x discontinueDate 2026-10-01 and constructs discontinued error prefix with selected range; code BUILD_UTILS_NODE_VERSION_DISCONTINUED. Prefix instantiated at20.x is source-derived, not a deployment observation."
622
+ },
623
+ {
624
+ "id": "next164-announcement",
625
+ "url": "https://nextjs.org/blog/next-16-4",
626
+ "notes": "Dated October 6,2026. New create-next-app apps enable Cache Components by default; existing apps require adoption. This is not a universal default switch for every existing app."
627
+ },
628
+ {
629
+ "id": "next-blocking-error",
630
+ "url": "https://nextjs.org/docs/messages/blocking-route",
631
+ "notes": "Official exact error title. With cacheComponents enabled, request-time async data needs parent Suspense. Cache deliberately reusable data with use cache, or move runtime read into child below Suspense. Build --debug-prerender may identify component."
632
+ },
633
+ {
634
+ "id": "next-cache-migration",
635
+ "url": "https://nextjs.org/docs/app/guides/migrating-to-cache-components",
636
+ "notes": "Route configs dynamic/revalidate/fetchCache replaced by use cache/cacheLife under Cache Components; avoid caching user request data indiscriminately."
637
+ },
638
+ {
639
+ "id": "lovable-environments",
640
+ "url": "https://docs.lovable.dev/features/environments",
641
+ "notes": "Current guide states retirement October 23,2026; detached Test databases restorable untilDecember 1,2026 then deleted. Built-in backend only. Drafts preview code with same database. Publishing schema/policies/functions does not copy rows/files/auth settings. Restore request required after detachment."
642
+ },
643
+ {
644
+ "id": "railway-cac",
645
+ "url": "https://docs.railway.com/config-as-code",
646
+ "notes": "Existing railway.json/toml services continue until 2026-12-01 hard cutoff; new services cannot opt into CaC. Prefer .railway/railway.ts."
647
+ },
648
+ {
649
+ "id": "railway-iac",
650
+ "url": "https://docs.railway.com/infrastructure-as-code",
651
+ "notes": "Review railway config plan before apply; whole-project omissions can delete resources; deployments do not read .railway directly. Migration section still claims --apply clears settings, conflicting with newer Oct 16 changelog's separate cutover."
652
+ },
653
+ {
654
+ "id": "railway-guided-migration",
655
+ "url": "https://railway.com/changelog/2026-10-16-activity-feed-filters",
656
+ "notes": "Dated Oct 16,2026. --apply writes config without switching services. migrate cutover lists effects/saves old paths; status reports and undo restores paths. Use newer scoped migration flow and installed CLI help rather than stale IaC snippet."
657
+ },
658
+ {
659
+ "id": "railway-cac-announcement",
660
+ "url": "https://railway.com/changelog/2026-08-20-railway-anon",
661
+ "notes": "Visible publish date 2026-08-21 despiteURLAug 20. Announces August 28 new-project restriction and December 1 end. Its older statement allows new services in existing projects; current CaC docs disallow new services, so avoid generalizing that exception."
662
+ },
663
+ {
664
+ "id": "clerk-production",
665
+ "url": "https://clerk.com/docs/guides/development/deployment/production",
666
+ "notes": "Evergreen current guidance: create/select production instance; use pk_live_/sk_live_ pair in production host vars then redeploy. Configure production OAuth/webhooks/DNS. This is verified Oct 30, not a newOct 30 rollout."
667
+ },
668
+ {
669
+ "id": "clerk-environments",
670
+ "url": "https://clerk.com/docs/guides/development/managing-environments",
671
+ "notes": "Development/Production instances differ; development unsuitable for production. Does not prove a particular app's live keys or readiness."
672
+ },
673
+ {
674
+ "id": "clerk-keys-once",
675
+ "url": "https://clerk.com/changelog/2026-10-19-secret-keys-visible-only-on-creation",
676
+ "notes": "Published Oct 19; URL supplies2026 and footer2026. Full secret value shown only on creation. Existing keys still work; if lost, add replacement, update code, delete old only after no longer used."
677
+ },
678
+ {
679
+ "id": "supabase-api-keys",
680
+ "url": "https://supabase.com/docs/guides/getting-started/api-keys",
681
+ "notes": "Current docs say legacy anon/service_role deprecated by end 2026, no exact shutdown date. Publishable/secret replace them; secret server-only/BYPASSRLS and browser rejectionHTTP401. New keys not JWTs; use apikey header, not Authorization bearer as a userJWT."
682
+ },
683
+ {
684
+ "id": "supabase-key-migration",
685
+ "url": "https://supabase.com/docs/guides/getting-started/migrating-to-new-api-keys",
686
+ "notes": "Create new keys alongside legacy; replace frontend anon with publishable and backend service_role with secret. Check components then disable legacy keys. Grant/RLS behavior retained, and key switch doesn't fix access policy."
687
+ }
688
+ ],
689
+ "entries": [
690
+ {
691
+ "id": "supabase-explicit-data-api-grants",
692
+ "provider": "supabase",
693
+ "date": "2026-10-30",
694
+ "dateKind": "effective",
695
+ "dateNote": "Provider-announced application date for existing projects; announced 2026-04-28. This is not verification that any particular hosted project has rolled over.",
696
+ "whatChanged": "After the rollout, new public tables need explicit role grants to be reachable through the Data/GraphQL API. Existing table grants remain; direct Postgres connections are unaffected.",
697
+ "errorText": "permission denied for table your_table",
698
+ "errorTextKind": "official_documentation_example",
699
+ "errorCode": "42501",
700
+ "fix": "Confirm the actual role/table/operation. In a reviewed migration, grant only required privileges (for example GRANT SELECT ON public.your_table TO authenticated), and keep RLS enabled with policies matching intended row access. Do not replace a missing grant with a server secret in browser code.",
701
+ "officialSource": "https://supabase.com/changelog/45329-breaking-change-tables-not-exposed-to-data-and-graphql-api-automatically",
702
+ "sourceIds": [
703
+ "supabase-grants-announcement",
704
+ "supabase-api-security"
705
+ ],
706
+ "limitations": "Repo inspection cannot establish hosted grants, actual rollout, policy behavior, or a successful live request."
707
+ },
708
+ {
709
+ "id": "vercel-node20-to24",
710
+ "provider": "vercel",
711
+ "date": "2026-10-01",
712
+ "dateKind": "effective",
713
+ "dateNote": "Announced 2026-07-14. Scope: new Builds/Functions deployments, not already-deployed function invocations.",
714
+ "whatChanged": "Node 20 is discontinued for new Builds/Functions deployments. Node 24 remains supported; current docs additionally list Node 26 as default, so 24 must not be described as today's default.",
715
+ "errorText": 'Node.js Version "20.x" is discontinued and must be upgraded.',
716
+ "errorTextKind": "official_source_template_instantiated",
717
+ "errorCode": "BUILD_UTILS_NODE_VERSION_DISCONTINUED",
718
+ "fix": "Change a Node 20 engines.node pin to 24.x, or select 24.x in Project Settings when engines is absent; engines overrides settings. Match local/CI runtime, reinstall dependencies, run build/tests, then verify the runtime in a future deployment. No deployment performed here.",
719
+ "officialSource": "https://vercel.com/changelog/node-js-20-is-being-deprecated",
720
+ "sourceIds": [
721
+ "vercel-node20-announcement",
722
+ "vercel-node-versions",
723
+ "vercel-node-error-source"
724
+ ],
725
+ "limitations": "Exact prefix comes from official source with 20.x substituted, not a newly observed build. Container deployments have a separate runtime model."
726
+ },
727
+ {
728
+ "id": "next-cache-components-suspense",
729
+ "provider": "nextjs",
730
+ "date": "2026-10-06",
731
+ "dateKind": "announced",
732
+ "dateNote": "Next 16.4 release date. Default enablement statement applies to newly generated create-next-app apps; existing app config must be inspected.",
733
+ "whatChanged": "Next 16.4 enables Cache Components in new create-next-app apps. With cacheComponents enabled, uncached request-time reads without a parent Suspense boundary trigger the documented error.",
734
+ "errorText": "Uncached data was accessed outside of `<Suspense>`",
735
+ "errorTextKind": "official_documentation_title",
736
+ "errorCode": null,
737
+ "fix": 'Move request-time reads into a child rendered under <Suspense fallback={...}>. For deliberately reusable data, use "use cache" with an appropriate lifetime. Migrate incompatible route configs such as dynamic/revalidate/fetchCache using the official guide, and build to verify.',
738
+ "officialSource": "https://nextjs.org/blog/next-16-4",
739
+ "sourceIds": [
740
+ "next164-announcement",
741
+ "next-blocking-error",
742
+ "next-cache-migration"
743
+ ],
744
+ "limitations": "No app/version-specific reproduction or build run. Do not cache authentication/request data indiscriminately."
745
+ },
746
+ {
747
+ "id": "lovable-test-live-retired",
748
+ "provider": "lovable",
749
+ "date": "2026-10-23",
750
+ "dateKind": "effective",
751
+ "dateNote": "Current official guide differs from seeded VibeRaven dates Oct 5/Nov 4. Current retirement Oct 23 and deletion Dec 1 verified Oct 30.",
752
+ "whatChanged": "Separate Test/Live on the built-in backend retired; projects use one database. Detached Test databases remain restorable by request until 2026-12-01, then are deleted. Drafts share data with the published app.",
753
+ "errorText": null,
754
+ "errorTextKind": "not_documented",
755
+ "symptom": "Test/Live switcher disappears; missing data may remain in detached Test rather than Live.",
756
+ "fix": "If needed data is in detached Test, request restoration before December 1, export needed rows/files and move them into Live, reconcile duplicates and verify Live content. Publishing alone does not migrate rows/files/auth settings. No account or data changes performed.",
757
+ "officialSource": "https://docs.lovable.dev/features/environments",
758
+ "sourceIds": [
759
+ "lovable-environments"
760
+ ],
761
+ "limitations": "Applies to built-in-backend projects that used the split, not every external Supabase project. No runtime error quote supplied by the guide."
762
+ },
763
+ {
764
+ "id": "railway-config-as-code-retirement",
765
+ "provider": "railway",
766
+ "date": "2026-12-01",
767
+ "dateKind": "effective",
768
+ "dateNote": "Upcoming hard cutoff documented today; announcement page visible date 2026-08-21 despite Aug 20 URL. Guided migration announced Oct 16.",
769
+ "whatChanged": "railway.json/railway.toml Config as Code is deprecated and stops working for existing services at Dec 1 cutoff. New services cannot opt in; prefer .railway/railway.ts IaC.",
770
+ "errorText": null,
771
+ "errorTextKind": "not_documented",
772
+ "symptom": "IaC plan is blocked for a service still managed by a CaC file; no exact cutoff failure message verified.",
773
+ "fix": "Preview with railway config migrate, inspect generated IaC, write with --apply, review separate migrate cutover using current CLI help, then migrate status and config plan. Review all changes/deletions before any authorized apply; committing .railway alone does not apply configuration.",
774
+ "officialSource": "https://docs.railway.com/config-as-code",
775
+ "sourceIds": [
776
+ "railway-cac",
777
+ "railway-iac",
778
+ "railway-guided-migration",
779
+ "railway-cac-announcement"
780
+ ],
781
+ "limitations": "Official IaC page still says --apply clears config settings; newer Oct 16 changelog explicitly separates cutover. No CLI/provider execution here; avoid unverified variables flags or predicting post-cutoff fallback."
782
+ },
783
+ {
784
+ "id": "clerk-production-instance-keys",
785
+ "provider": "clerk",
786
+ "date": "2026-10-30",
787
+ "dateKind": "verified",
788
+ "dateNote": "Verification date only for evergreen production-instance guidance, not a rollout date. Related show-secret-once change announced 2026-10-19.",
789
+ "whatChanged": "Current production deployment guidance requires production-instance pk_live_/sk_live_ keys. Separately, since the Oct 19 announcement, existing secret values are masked and full values appear only when created.",
790
+ "errorText": null,
791
+ "errorTextKind": "not_documented",
792
+ "symptom": "Production app still uses pk_test_/sk_test_, or a lost secret cannot be revealed again.",
793
+ "fix": "Use matching production-instance keys in the production host environment and redeploy, with production OAuth/webhook/DNS configuration checked. If a secret value is lost, create a replacement, update all consuming components, then delete the old one only after it is unused. Existing keys are not invalidated merely by masking.",
794
+ "officialSource": "https://clerk.com/docs/guides/development/deployment/production",
795
+ "sourceIds": [
796
+ "clerk-production",
797
+ "clerk-environments",
798
+ "clerk-keys-once"
799
+ ],
800
+ "limitations": "No account, secret, production-instance, redirect, or deployment inspection. These docs give no single exact runtime error for the whole symptom."
801
+ },
802
+ {
803
+ "id": "supabase-publishable-secret-api-keys",
804
+ "provider": "supabase",
805
+ "date": "2026-10-30",
806
+ "dateKind": "verified",
807
+ "dateNote": "Verification date only. Docs say legacy keys deprecated by end 2026; no exact shutdown day claimed or checked here.",
808
+ "whatChanged": "Publishable (sb_publishable_) and secret (sb_secret_) replace legacy anon/service_role keys. New keys are not JWTs; both systems can coexist during migration.",
809
+ "errorText": "HTTP 401 Unauthorized",
810
+ "errorTextKind": "official_documented_http_status",
811
+ "symptom": "A secret key sent with a browser User-Agent is rejected; this is not a guarantee against use from scripts.",
812
+ "fix": "Replace public/client anon usage with publishable and backend service_role usage with secret; keep privileged keys out of client code. Send API keys through apikey; use actual user JWTs for user Authorization. Verify all clients before disabling legacy keys. Rotate a leaked secret after fixing its exposure.",
813
+ "officialSource": "https://supabase.com/docs/guides/getting-started/api-keys",
814
+ "sourceIds": [
815
+ "supabase-api-keys",
816
+ "supabase-key-migration"
817
+ ],
818
+ "limitations": "No key/account/provider inspection, rotation, or live request. Switching key formats does not fix missing grants or RLS policies."
819
+ }
820
+ ]
821
+ }
822
+ };
823
+
824
+ // ../providers/recentChanges.mjs
825
+ var availableProviders = [...new Set(recent_changes_generated_default.pack.entries.map((entry) => entry.provider))].sort();
826
+ var RECENT_PROVIDER_CHANGES_TOOL = {
827
+ name: "recent_provider_changes",
828
+ title: "Check recent provider changes",
829
+ description: `Check dated official provider guidance before answering a provider error or updating a deployment. Returns candidate changes, documented errors or symptoms, fixes, date meanings and official supporting sources. Filter by provider or redacted error keywords. Available providers: ${availableProviders.join(", ")}.
830
+ Limits: guidance only; does not read your repo, connect to providers, run fixes or verify rollout, deployment or live behavior.`,
831
+ inputSchema: {
832
+ type: "object",
833
+ properties: {
834
+ provider: { type: "string", enum: [...availableProviders], description: "Optional lowercase provider id. Unsupported ids return the bounded available list." },
835
+ query: { type: "string", minLength: 1, maxLength: 500, description: "Optional redacted error text or public keywords. Remove credentials, private paths and personal data before calling." },
836
+ limit: { type: "integer", minimum: 1, maximum: 8, default: 5, description: "Maximum entries, 1 to 8; default 5." }
837
+ },
838
+ additionalProperties: false
839
+ },
840
+ outputSchema: {
841
+ type: "object",
842
+ properties: { packVersion: { type: "string" }, packHash: { type: "string" }, reviewedAt: { type: "string" }, dateConvention: { type: "string" }, entries: { type: "array", items: { type: "object" }, maxItems: 8 }, availableProviders: { type: "array", items: { type: "string" } }, limits: { type: "array", items: { type: "string" } }, correctionsAndConflicts: { type: "array", items: { type: "string" } }, verification: { type: "object" } },
843
+ required: ["packVersion", "packHash", "reviewedAt", "dateConvention", "entries", "availableProviders", "limits", "correctionsAndConflicts", "verification"],
844
+ additionalProperties: false
845
+ },
846
+ annotations: { title: "Check recent provider changes", readOnlyHint: true, destructiveHint: false, openWorldHint: false, idempotentHint: true }
847
+ };
848
+ var stopWords = /* @__PURE__ */ new Set([...availableProviders, "next", "js", ..."a an and app apps are as at be before by can does error for from has have how in is it not of on or provider the this to was what when which with".split(" ")]);
849
+ var words = (text) => [...new Set((text.toLowerCase().match(/[a-z0-9_]+/g) ?? []).filter((word) => (word.length >= 3 || /^\d{2,}$/.test(word)) && !stopWords.has(word)))];
850
+ var indexed = recent_changes_generated_default.pack.entries.map((entry) => ({ entry, words: new Set(words([entry.id, entry.provider, entry.whatChanged, entry.errorText, entry.errorCode, entry.symptom, entry.fix].filter(Boolean).join(" "))) }));
851
+ function invalidInput(field) {
852
+ return { isError: true, content: [{ type: "text", text: `invalid_input: Use optional supported provider, redacted query (1 to 500 characters), and limit (integer 1 to 8).
853
+ Field: ${field}
854
+ Example arguments: {"provider":"supabase","query":"42501","limit":5}
855
+ Next step: Choose an available provider: ${availableProviders.join(", ")}. Retrieval returns guidance; no connection or check was attempted.` }] };
856
+ }
857
+ function renderRecentChanges(result) {
858
+ const lines = [`Recent provider changes ${result.packVersion} (reviewed ${result.reviewedAt})`, result.dateConvention, "Guidance only. Repository and live checks: not checked.", ""];
859
+ if (!result.entries.length) lines.push("No entry matched. A missing match does not rule out a provider change; inspect the current official documentation and actual app evidence.");
860
+ for (const entry of result.entries) {
861
+ lines.push(`${entry.provider}: ${entry.id}`, `Date: ${entry.date} (${entry.dateKind}). ${entry.dateNote}`, `What changed: ${entry.whatChanged}`);
862
+ if (entry.errorText !== null) lines.push(`Error: ${entry.errorText} (${entry.errorTextKind}${entry.errorCode ? `; code ${entry.errorCode}` : ""})`);
863
+ else lines.push(`Error: no exact error documented (${entry.errorTextKind}).`);
864
+ if (entry.symptom) lines.push(`Symptom: ${entry.symptom}`);
865
+ lines.push(`Fix guidance: ${entry.fix}`, `Official source: ${entry.officialSource}`, `Supporting sources: ${entry.sources.map((source) => source.url).join(" ")}`, `Limits: ${entry.limitations}`, "");
866
+ }
867
+ lines.push("Source corrections and conflicts:", ...result.correctionsAndConflicts.map((note) => `- ${note}`), "Limits:", ...result.limits.map((limit) => `- ${limit}`));
868
+ return lines.join("\n");
869
+ }
870
+ function recentProviderChanges(args) {
871
+ if (!args || typeof args !== "object" || Array.isArray(args) || Object.keys(args).some((key) => !["provider", "query", "limit"].includes(key))) return invalidInput("arguments");
872
+ if (Object.hasOwn(args, "provider") && (typeof args.provider !== "string" || !availableProviders.includes(args.provider))) return invalidInput("provider");
873
+ if (Object.hasOwn(args, "query") && (typeof args.query !== "string" || args.query.length > 500 || !args.query.trim() || /\u0000/.test(args.query))) return invalidInput("query");
874
+ if (Object.hasOwn(args, "limit") && (!Number.isInteger(args.limit) || args.limit < 1 || args.limit > 8)) return invalidInput("limit");
875
+ const terms = args.query === void 0 ? null : words(args.query);
876
+ const entries = indexed.filter((item) => args.provider === void 0 || item.entry.provider === args.provider).map((item) => ({ ...item, score: terms === null ? 0 : terms.reduce((score, term) => score + Number(item.words.has(term)), 0) })).filter((item) => terms === null || item.score > 0).sort((a, b) => b.score - a.score).slice(0, args.limit ?? 5).map(({ entry }) => ({ ...entry, sources: entry.sourceIds.map((id2) => recent_changes_generated_default.pack.sources.find((source) => source.id === id2)) }));
877
+ const structuredContent = JSON.parse(JSON.stringify({
878
+ packVersion: recent_changes_generated_default.pack.packVersion,
879
+ packHash: recent_changes_generated_default.hash,
880
+ reviewedAt: recent_changes_generated_default.pack.reviewedAt,
881
+ dateConvention: recent_changes_generated_default.pack.dateConvention,
882
+ entries,
883
+ availableProviders,
884
+ limits: recent_changes_generated_default.pack.limits,
885
+ correctionsAndConflicts: recent_changes_generated_default.pack.correctionsAndConflicts,
886
+ verification: { repo: "not_checked", live: "not_checked" }
887
+ }));
888
+ return { isError: false, structuredContent, content: [{ type: "text", text: renderRecentChanges(structuredContent) }] };
889
+ }
890
+
576
891
  // ../providers/index.mjs
577
892
  var PROVIDER_TOOL = {
578
893
  name: "provider_playbook",
@@ -1185,7 +1500,7 @@ function mcpVersion() {
1185
1500
  } catch {
1186
1501
  }
1187
1502
  }
1188
- found ??= true ? "1.7.1" : void 0;
1503
+ found ??= true ? "1.7.2" : void 0;
1189
1504
  if (!found || !PLAIN_VERSION.test(found)) {
1190
1505
  throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
1191
1506
  }
@@ -1400,6 +1715,7 @@ var ALL_TOOLS = [
1400
1715
  ...npmTools,
1401
1716
  ...WORK_TOOLS,
1402
1717
  PROVIDER_TOOL,
1718
+ RECENT_PROVIDER_CHANGES_TOOL,
1403
1719
  ...LIVE_TOOLS
1404
1720
  ];
1405
1721
  function parseJsonObjectFromToolText(text) {
@@ -1427,6 +1743,7 @@ async function handleRequest(method, params) {
1427
1743
  if (method === "tools/list") return { tools: ALL_TOOLS };
1428
1744
  if (method === "tools/call") {
1429
1745
  if (params.name === "provider_playbook") return providerPlaybook(params.arguments);
1746
+ if (params.name === "recent_provider_changes") return recentProviderChanges(params.arguments ?? {});
1430
1747
  const args = params.arguments || {};
1431
1748
  const cliArgs = buildToolArgs(params.name, args);
1432
1749
  const run = await runVibeRavenDetailed(cliArgs, args.cwd);
@@ -1449,7 +1766,7 @@ async function handleRequest(method, params) {
1449
1766
  }
1450
1767
 
1451
1768
  // src/server.ts
1452
- var SERVER_INFO = { name: "viberaven-mcp", version: "1.7.1" };
1769
+ var SERVER_INFO = { name: "viberaven-mcp", version: "1.7.2" };
1453
1770
  var INSTRUCTIONS = [
1454
1771
  "VibeRaven reads a repository and lists launch gaps for AI-built apps that deploy on Vercel and use Supabase.",
1455
1772
  "Suggest one viberaven_check_readiness run before such an app launches or is handed off, after a Supabase migration or policy change,",
@@ -1458,6 +1775,7 @@ var INSTRUCTIONS = [
1458
1775
  "It is a repository check, not a live database test. It cannot show which RLS policies are live in production, and a clear result is not a security audit.",
1459
1776
  "The existing repository checks are scoped to Vercel and Supabase; they do not cover every provider.",
1460
1777
  "For feature planning, provider_playbook returns versioned provider knowledge independently of hosting. Read the supported pack and its limits; retrieval does not execute checks or connect to providers.",
1778
+ "Check recent_provider_changes before answering a provider error or updating a deployment. Pass redacted error keywords; dates and official sources give candidate explanations, not a diagnosis or proof of live state.",
1461
1779
  "For optional behavioral checks after reviewing a Supabase migration or ownership policy, viberaven_rls_test runs an already reviewed local permissions matrix for owner, other_user and anon. Read Pass, Fail and Unknown per cell; Unknown is inconclusive. This experimental PGlite imitation is not live Supabase proof. PGlite must already be installed next to the matching CLI used by the local MCP host; missing setup is a tool error with CLI guidance, not a passing result.",
1462
1780
  "After fixes, call viberaven_verify once per batch, not after every edit."
1463
1781
  ].join(" ");
@@ -573,6 +573,321 @@ var registry_generated_default = {
573
573
  }
574
574
  };
575
575
 
576
+ // ../providers/recent-changes.generated.mjs
577
+ var recent_changes_generated_default = {
578
+ "hash": "d2aaaaf9089270914954d2a8fd7b4fa3933c8525111162650feeb7bf726c67dc",
579
+ "pack": {
580
+ "schemaVersion": 1,
581
+ "packVersion": "1.0.0",
582
+ "reviewedAt": "2026-10-30",
583
+ "dateConvention": "effective = provider-stated date; announced = publication/release date; verified = checked date only, not rollout.",
584
+ "limits": [
585
+ "Guidance only; repository and live provider state remain not_checked.",
586
+ "Static, reviewed official sources can change. A matching entry is a candidate explanation, not a diagnosis or evidence that a fix worked.",
587
+ "No provider connection, account, credential, runtime file read, network request, deployment or data change is performed."
588
+ ],
589
+ "correctionsAndConflicts": [
590
+ "Lovable current official dates Oct 23 retirement/Dec 1 deletion replace seeded Oct5/Nov 4. Affected built-in-backend projects only.",
591
+ "Vercel current docs list 26.x default; 24.x remains supported but is not the current default claim.",
592
+ "Railway IaC migration doc says --apply clears settings, but newer Oct 16 changelog explicitly requires separate cutover. Current CLI help must be inspected before execution.",
593
+ "Railway announcement has2026-08-21 visible publish date despite Aug 20 URL; avoid inventing Aug 20 announced date.",
594
+ "Clerk production-instance setup is evergreen verified Oct 30, not an Oct 30 provider change. Related secret masking is dated Oct 19.",
595
+ "Supabase legacy-key end 2026 deprecation is not an exact shutdown day; no mandatory day invented."
596
+ ],
597
+ "sources": [
598
+ {
599
+ "id": "supabase-grants-announcement",
600
+ "url": "https://supabase.com/changelog/45329-breaking-change-tables-not-exposed-to-data-and-graphql-api-automatically",
601
+ "notes": "Dated April 28, 2026. Announces October 30 application to existing projects; newly created public tables need explicit grants. Existing table grants persist; direct Postgres users unaffected. Official example uses code 42501 and permission denied for table your_table."
602
+ },
603
+ {
604
+ "id": "supabase-api-security",
605
+ "url": "https://supabase.com/docs/guides/api/securing-your-api",
606
+ "notes": "Grants determine object/role access; RLS controls rows. Configure both for API-exposed tables. Does not prove hosted project rollout or actual grants."
607
+ },
608
+ {
609
+ "id": "vercel-node20-announcement",
610
+ "url": "https://vercel.com/changelog/node-js-20-is-being-deprecated",
611
+ "notes": "Published July 14, 2026. October 1 deprecation for Builds/Functions affects new deployments, not existing invocations. Official upgrade example sets engines.node to 24.x, matches local/CI and reruns build/tests."
612
+ },
613
+ {
614
+ "id": "vercel-node-versions",
615
+ "url": "https://vercel.com/docs/functions/runtimes/node-js/node-js-versions",
616
+ "notes": "Current docs list 26.x default and 24.x/22.x supported. package.json engines.node overrides Project Settings. Do not repeat seed's 24.x default claim."
617
+ },
618
+ {
619
+ "id": "vercel-node-error-source",
620
+ "url": "https://raw.githubusercontent.com/vercel/vercel/main/packages/build-utils/src/fs/node-version.ts",
621
+ "notes": "Official mutable main source lists20.x discontinueDate 2026-10-01 and constructs discontinued error prefix with selected range; code BUILD_UTILS_NODE_VERSION_DISCONTINUED. Prefix instantiated at20.x is source-derived, not a deployment observation."
622
+ },
623
+ {
624
+ "id": "next164-announcement",
625
+ "url": "https://nextjs.org/blog/next-16-4",
626
+ "notes": "Dated October 6,2026. New create-next-app apps enable Cache Components by default; existing apps require adoption. This is not a universal default switch for every existing app."
627
+ },
628
+ {
629
+ "id": "next-blocking-error",
630
+ "url": "https://nextjs.org/docs/messages/blocking-route",
631
+ "notes": "Official exact error title. With cacheComponents enabled, request-time async data needs parent Suspense. Cache deliberately reusable data with use cache, or move runtime read into child below Suspense. Build --debug-prerender may identify component."
632
+ },
633
+ {
634
+ "id": "next-cache-migration",
635
+ "url": "https://nextjs.org/docs/app/guides/migrating-to-cache-components",
636
+ "notes": "Route configs dynamic/revalidate/fetchCache replaced by use cache/cacheLife under Cache Components; avoid caching user request data indiscriminately."
637
+ },
638
+ {
639
+ "id": "lovable-environments",
640
+ "url": "https://docs.lovable.dev/features/environments",
641
+ "notes": "Current guide states retirement October 23,2026; detached Test databases restorable untilDecember 1,2026 then deleted. Built-in backend only. Drafts preview code with same database. Publishing schema/policies/functions does not copy rows/files/auth settings. Restore request required after detachment."
642
+ },
643
+ {
644
+ "id": "railway-cac",
645
+ "url": "https://docs.railway.com/config-as-code",
646
+ "notes": "Existing railway.json/toml services continue until 2026-12-01 hard cutoff; new services cannot opt into CaC. Prefer .railway/railway.ts."
647
+ },
648
+ {
649
+ "id": "railway-iac",
650
+ "url": "https://docs.railway.com/infrastructure-as-code",
651
+ "notes": "Review railway config plan before apply; whole-project omissions can delete resources; deployments do not read .railway directly. Migration section still claims --apply clears settings, conflicting with newer Oct 16 changelog's separate cutover."
652
+ },
653
+ {
654
+ "id": "railway-guided-migration",
655
+ "url": "https://railway.com/changelog/2026-10-16-activity-feed-filters",
656
+ "notes": "Dated Oct 16,2026. --apply writes config without switching services. migrate cutover lists effects/saves old paths; status reports and undo restores paths. Use newer scoped migration flow and installed CLI help rather than stale IaC snippet."
657
+ },
658
+ {
659
+ "id": "railway-cac-announcement",
660
+ "url": "https://railway.com/changelog/2026-08-20-railway-anon",
661
+ "notes": "Visible publish date 2026-08-21 despiteURLAug 20. Announces August 28 new-project restriction and December 1 end. Its older statement allows new services in existing projects; current CaC docs disallow new services, so avoid generalizing that exception."
662
+ },
663
+ {
664
+ "id": "clerk-production",
665
+ "url": "https://clerk.com/docs/guides/development/deployment/production",
666
+ "notes": "Evergreen current guidance: create/select production instance; use pk_live_/sk_live_ pair in production host vars then redeploy. Configure production OAuth/webhooks/DNS. This is verified Oct 30, not a newOct 30 rollout."
667
+ },
668
+ {
669
+ "id": "clerk-environments",
670
+ "url": "https://clerk.com/docs/guides/development/managing-environments",
671
+ "notes": "Development/Production instances differ; development unsuitable for production. Does not prove a particular app's live keys or readiness."
672
+ },
673
+ {
674
+ "id": "clerk-keys-once",
675
+ "url": "https://clerk.com/changelog/2026-10-19-secret-keys-visible-only-on-creation",
676
+ "notes": "Published Oct 19; URL supplies2026 and footer2026. Full secret value shown only on creation. Existing keys still work; if lost, add replacement, update code, delete old only after no longer used."
677
+ },
678
+ {
679
+ "id": "supabase-api-keys",
680
+ "url": "https://supabase.com/docs/guides/getting-started/api-keys",
681
+ "notes": "Current docs say legacy anon/service_role deprecated by end 2026, no exact shutdown date. Publishable/secret replace them; secret server-only/BYPASSRLS and browser rejectionHTTP401. New keys not JWTs; use apikey header, not Authorization bearer as a userJWT."
682
+ },
683
+ {
684
+ "id": "supabase-key-migration",
685
+ "url": "https://supabase.com/docs/guides/getting-started/migrating-to-new-api-keys",
686
+ "notes": "Create new keys alongside legacy; replace frontend anon with publishable and backend service_role with secret. Check components then disable legacy keys. Grant/RLS behavior retained, and key switch doesn't fix access policy."
687
+ }
688
+ ],
689
+ "entries": [
690
+ {
691
+ "id": "supabase-explicit-data-api-grants",
692
+ "provider": "supabase",
693
+ "date": "2026-10-30",
694
+ "dateKind": "effective",
695
+ "dateNote": "Provider-announced application date for existing projects; announced 2026-04-28. This is not verification that any particular hosted project has rolled over.",
696
+ "whatChanged": "After the rollout, new public tables need explicit role grants to be reachable through the Data/GraphQL API. Existing table grants remain; direct Postgres connections are unaffected.",
697
+ "errorText": "permission denied for table your_table",
698
+ "errorTextKind": "official_documentation_example",
699
+ "errorCode": "42501",
700
+ "fix": "Confirm the actual role/table/operation. In a reviewed migration, grant only required privileges (for example GRANT SELECT ON public.your_table TO authenticated), and keep RLS enabled with policies matching intended row access. Do not replace a missing grant with a server secret in browser code.",
701
+ "officialSource": "https://supabase.com/changelog/45329-breaking-change-tables-not-exposed-to-data-and-graphql-api-automatically",
702
+ "sourceIds": [
703
+ "supabase-grants-announcement",
704
+ "supabase-api-security"
705
+ ],
706
+ "limitations": "Repo inspection cannot establish hosted grants, actual rollout, policy behavior, or a successful live request."
707
+ },
708
+ {
709
+ "id": "vercel-node20-to24",
710
+ "provider": "vercel",
711
+ "date": "2026-10-01",
712
+ "dateKind": "effective",
713
+ "dateNote": "Announced 2026-07-14. Scope: new Builds/Functions deployments, not already-deployed function invocations.",
714
+ "whatChanged": "Node 20 is discontinued for new Builds/Functions deployments. Node 24 remains supported; current docs additionally list Node 26 as default, so 24 must not be described as today's default.",
715
+ "errorText": 'Node.js Version "20.x" is discontinued and must be upgraded.',
716
+ "errorTextKind": "official_source_template_instantiated",
717
+ "errorCode": "BUILD_UTILS_NODE_VERSION_DISCONTINUED",
718
+ "fix": "Change a Node 20 engines.node pin to 24.x, or select 24.x in Project Settings when engines is absent; engines overrides settings. Match local/CI runtime, reinstall dependencies, run build/tests, then verify the runtime in a future deployment. No deployment performed here.",
719
+ "officialSource": "https://vercel.com/changelog/node-js-20-is-being-deprecated",
720
+ "sourceIds": [
721
+ "vercel-node20-announcement",
722
+ "vercel-node-versions",
723
+ "vercel-node-error-source"
724
+ ],
725
+ "limitations": "Exact prefix comes from official source with 20.x substituted, not a newly observed build. Container deployments have a separate runtime model."
726
+ },
727
+ {
728
+ "id": "next-cache-components-suspense",
729
+ "provider": "nextjs",
730
+ "date": "2026-10-06",
731
+ "dateKind": "announced",
732
+ "dateNote": "Next 16.4 release date. Default enablement statement applies to newly generated create-next-app apps; existing app config must be inspected.",
733
+ "whatChanged": "Next 16.4 enables Cache Components in new create-next-app apps. With cacheComponents enabled, uncached request-time reads without a parent Suspense boundary trigger the documented error.",
734
+ "errorText": "Uncached data was accessed outside of `<Suspense>`",
735
+ "errorTextKind": "official_documentation_title",
736
+ "errorCode": null,
737
+ "fix": 'Move request-time reads into a child rendered under <Suspense fallback={...}>. For deliberately reusable data, use "use cache" with an appropriate lifetime. Migrate incompatible route configs such as dynamic/revalidate/fetchCache using the official guide, and build to verify.',
738
+ "officialSource": "https://nextjs.org/blog/next-16-4",
739
+ "sourceIds": [
740
+ "next164-announcement",
741
+ "next-blocking-error",
742
+ "next-cache-migration"
743
+ ],
744
+ "limitations": "No app/version-specific reproduction or build run. Do not cache authentication/request data indiscriminately."
745
+ },
746
+ {
747
+ "id": "lovable-test-live-retired",
748
+ "provider": "lovable",
749
+ "date": "2026-10-23",
750
+ "dateKind": "effective",
751
+ "dateNote": "Current official guide differs from seeded VibeRaven dates Oct 5/Nov 4. Current retirement Oct 23 and deletion Dec 1 verified Oct 30.",
752
+ "whatChanged": "Separate Test/Live on the built-in backend retired; projects use one database. Detached Test databases remain restorable by request until 2026-12-01, then are deleted. Drafts share data with the published app.",
753
+ "errorText": null,
754
+ "errorTextKind": "not_documented",
755
+ "symptom": "Test/Live switcher disappears; missing data may remain in detached Test rather than Live.",
756
+ "fix": "If needed data is in detached Test, request restoration before December 1, export needed rows/files and move them into Live, reconcile duplicates and verify Live content. Publishing alone does not migrate rows/files/auth settings. No account or data changes performed.",
757
+ "officialSource": "https://docs.lovable.dev/features/environments",
758
+ "sourceIds": [
759
+ "lovable-environments"
760
+ ],
761
+ "limitations": "Applies to built-in-backend projects that used the split, not every external Supabase project. No runtime error quote supplied by the guide."
762
+ },
763
+ {
764
+ "id": "railway-config-as-code-retirement",
765
+ "provider": "railway",
766
+ "date": "2026-12-01",
767
+ "dateKind": "effective",
768
+ "dateNote": "Upcoming hard cutoff documented today; announcement page visible date 2026-08-21 despite Aug 20 URL. Guided migration announced Oct 16.",
769
+ "whatChanged": "railway.json/railway.toml Config as Code is deprecated and stops working for existing services at Dec 1 cutoff. New services cannot opt in; prefer .railway/railway.ts IaC.",
770
+ "errorText": null,
771
+ "errorTextKind": "not_documented",
772
+ "symptom": "IaC plan is blocked for a service still managed by a CaC file; no exact cutoff failure message verified.",
773
+ "fix": "Preview with railway config migrate, inspect generated IaC, write with --apply, review separate migrate cutover using current CLI help, then migrate status and config plan. Review all changes/deletions before any authorized apply; committing .railway alone does not apply configuration.",
774
+ "officialSource": "https://docs.railway.com/config-as-code",
775
+ "sourceIds": [
776
+ "railway-cac",
777
+ "railway-iac",
778
+ "railway-guided-migration",
779
+ "railway-cac-announcement"
780
+ ],
781
+ "limitations": "Official IaC page still says --apply clears config settings; newer Oct 16 changelog explicitly separates cutover. No CLI/provider execution here; avoid unverified variables flags or predicting post-cutoff fallback."
782
+ },
783
+ {
784
+ "id": "clerk-production-instance-keys",
785
+ "provider": "clerk",
786
+ "date": "2026-10-30",
787
+ "dateKind": "verified",
788
+ "dateNote": "Verification date only for evergreen production-instance guidance, not a rollout date. Related show-secret-once change announced 2026-10-19.",
789
+ "whatChanged": "Current production deployment guidance requires production-instance pk_live_/sk_live_ keys. Separately, since the Oct 19 announcement, existing secret values are masked and full values appear only when created.",
790
+ "errorText": null,
791
+ "errorTextKind": "not_documented",
792
+ "symptom": "Production app still uses pk_test_/sk_test_, or a lost secret cannot be revealed again.",
793
+ "fix": "Use matching production-instance keys in the production host environment and redeploy, with production OAuth/webhook/DNS configuration checked. If a secret value is lost, create a replacement, update all consuming components, then delete the old one only after it is unused. Existing keys are not invalidated merely by masking.",
794
+ "officialSource": "https://clerk.com/docs/guides/development/deployment/production",
795
+ "sourceIds": [
796
+ "clerk-production",
797
+ "clerk-environments",
798
+ "clerk-keys-once"
799
+ ],
800
+ "limitations": "No account, secret, production-instance, redirect, or deployment inspection. These docs give no single exact runtime error for the whole symptom."
801
+ },
802
+ {
803
+ "id": "supabase-publishable-secret-api-keys",
804
+ "provider": "supabase",
805
+ "date": "2026-10-30",
806
+ "dateKind": "verified",
807
+ "dateNote": "Verification date only. Docs say legacy keys deprecated by end 2026; no exact shutdown day claimed or checked here.",
808
+ "whatChanged": "Publishable (sb_publishable_) and secret (sb_secret_) replace legacy anon/service_role keys. New keys are not JWTs; both systems can coexist during migration.",
809
+ "errorText": "HTTP 401 Unauthorized",
810
+ "errorTextKind": "official_documented_http_status",
811
+ "symptom": "A secret key sent with a browser User-Agent is rejected; this is not a guarantee against use from scripts.",
812
+ "fix": "Replace public/client anon usage with publishable and backend service_role usage with secret; keep privileged keys out of client code. Send API keys through apikey; use actual user JWTs for user Authorization. Verify all clients before disabling legacy keys. Rotate a leaked secret after fixing its exposure.",
813
+ "officialSource": "https://supabase.com/docs/guides/getting-started/api-keys",
814
+ "sourceIds": [
815
+ "supabase-api-keys",
816
+ "supabase-key-migration"
817
+ ],
818
+ "limitations": "No key/account/provider inspection, rotation, or live request. Switching key formats does not fix missing grants or RLS policies."
819
+ }
820
+ ]
821
+ }
822
+ };
823
+
824
+ // ../providers/recentChanges.mjs
825
+ var availableProviders = [...new Set(recent_changes_generated_default.pack.entries.map((entry) => entry.provider))].sort();
826
+ var RECENT_PROVIDER_CHANGES_TOOL = {
827
+ name: "recent_provider_changes",
828
+ title: "Check recent provider changes",
829
+ description: `Check dated official provider guidance before answering a provider error or updating a deployment. Returns candidate changes, documented errors or symptoms, fixes, date meanings and official supporting sources. Filter by provider or redacted error keywords. Available providers: ${availableProviders.join(", ")}.
830
+ Limits: guidance only; does not read your repo, connect to providers, run fixes or verify rollout, deployment or live behavior.`,
831
+ inputSchema: {
832
+ type: "object",
833
+ properties: {
834
+ provider: { type: "string", enum: [...availableProviders], description: "Optional lowercase provider id. Unsupported ids return the bounded available list." },
835
+ query: { type: "string", minLength: 1, maxLength: 500, description: "Optional redacted error text or public keywords. Remove credentials, private paths and personal data before calling." },
836
+ limit: { type: "integer", minimum: 1, maximum: 8, default: 5, description: "Maximum entries, 1 to 8; default 5." }
837
+ },
838
+ additionalProperties: false
839
+ },
840
+ outputSchema: {
841
+ type: "object",
842
+ properties: { packVersion: { type: "string" }, packHash: { type: "string" }, reviewedAt: { type: "string" }, dateConvention: { type: "string" }, entries: { type: "array", items: { type: "object" }, maxItems: 8 }, availableProviders: { type: "array", items: { type: "string" } }, limits: { type: "array", items: { type: "string" } }, correctionsAndConflicts: { type: "array", items: { type: "string" } }, verification: { type: "object" } },
843
+ required: ["packVersion", "packHash", "reviewedAt", "dateConvention", "entries", "availableProviders", "limits", "correctionsAndConflicts", "verification"],
844
+ additionalProperties: false
845
+ },
846
+ annotations: { title: "Check recent provider changes", readOnlyHint: true, destructiveHint: false, openWorldHint: false, idempotentHint: true }
847
+ };
848
+ var stopWords = /* @__PURE__ */ new Set([...availableProviders, "next", "js", ..."a an and app apps are as at be before by can does error for from has have how in is it not of on or provider the this to was what when which with".split(" ")]);
849
+ var words = (text) => [...new Set((text.toLowerCase().match(/[a-z0-9_]+/g) ?? []).filter((word) => (word.length >= 3 || /^\d{2,}$/.test(word)) && !stopWords.has(word)))];
850
+ var indexed = recent_changes_generated_default.pack.entries.map((entry) => ({ entry, words: new Set(words([entry.id, entry.provider, entry.whatChanged, entry.errorText, entry.errorCode, entry.symptom, entry.fix].filter(Boolean).join(" "))) }));
851
+ function invalidInput(field) {
852
+ return { isError: true, content: [{ type: "text", text: `invalid_input: Use optional supported provider, redacted query (1 to 500 characters), and limit (integer 1 to 8).
853
+ Field: ${field}
854
+ Example arguments: {"provider":"supabase","query":"42501","limit":5}
855
+ Next step: Choose an available provider: ${availableProviders.join(", ")}. Retrieval returns guidance; no connection or check was attempted.` }] };
856
+ }
857
+ function renderRecentChanges(result) {
858
+ const lines = [`Recent provider changes ${result.packVersion} (reviewed ${result.reviewedAt})`, result.dateConvention, "Guidance only. Repository and live checks: not checked.", ""];
859
+ if (!result.entries.length) lines.push("No entry matched. A missing match does not rule out a provider change; inspect the current official documentation and actual app evidence.");
860
+ for (const entry of result.entries) {
861
+ lines.push(`${entry.provider}: ${entry.id}`, `Date: ${entry.date} (${entry.dateKind}). ${entry.dateNote}`, `What changed: ${entry.whatChanged}`);
862
+ if (entry.errorText !== null) lines.push(`Error: ${entry.errorText} (${entry.errorTextKind}${entry.errorCode ? `; code ${entry.errorCode}` : ""})`);
863
+ else lines.push(`Error: no exact error documented (${entry.errorTextKind}).`);
864
+ if (entry.symptom) lines.push(`Symptom: ${entry.symptom}`);
865
+ lines.push(`Fix guidance: ${entry.fix}`, `Official source: ${entry.officialSource}`, `Supporting sources: ${entry.sources.map((source) => source.url).join(" ")}`, `Limits: ${entry.limitations}`, "");
866
+ }
867
+ lines.push("Source corrections and conflicts:", ...result.correctionsAndConflicts.map((note) => `- ${note}`), "Limits:", ...result.limits.map((limit) => `- ${limit}`));
868
+ return lines.join("\n");
869
+ }
870
+ function recentProviderChanges(args) {
871
+ if (!args || typeof args !== "object" || Array.isArray(args) || Object.keys(args).some((key) => !["provider", "query", "limit"].includes(key))) return invalidInput("arguments");
872
+ if (Object.hasOwn(args, "provider") && (typeof args.provider !== "string" || !availableProviders.includes(args.provider))) return invalidInput("provider");
873
+ if (Object.hasOwn(args, "query") && (typeof args.query !== "string" || args.query.length > 500 || !args.query.trim() || /\u0000/.test(args.query))) return invalidInput("query");
874
+ if (Object.hasOwn(args, "limit") && (!Number.isInteger(args.limit) || args.limit < 1 || args.limit > 8)) return invalidInput("limit");
875
+ const terms = args.query === void 0 ? null : words(args.query);
876
+ const entries = indexed.filter((item) => args.provider === void 0 || item.entry.provider === args.provider).map((item) => ({ ...item, score: terms === null ? 0 : terms.reduce((score, term) => score + Number(item.words.has(term)), 0) })).filter((item) => terms === null || item.score > 0).sort((a, b) => b.score - a.score).slice(0, args.limit ?? 5).map(({ entry }) => ({ ...entry, sources: entry.sourceIds.map((id2) => recent_changes_generated_default.pack.sources.find((source) => source.id === id2)) }));
877
+ const structuredContent = JSON.parse(JSON.stringify({
878
+ packVersion: recent_changes_generated_default.pack.packVersion,
879
+ packHash: recent_changes_generated_default.hash,
880
+ reviewedAt: recent_changes_generated_default.pack.reviewedAt,
881
+ dateConvention: recent_changes_generated_default.pack.dateConvention,
882
+ entries,
883
+ availableProviders,
884
+ limits: recent_changes_generated_default.pack.limits,
885
+ correctionsAndConflicts: recent_changes_generated_default.pack.correctionsAndConflicts,
886
+ verification: { repo: "not_checked", live: "not_checked" }
887
+ }));
888
+ return { isError: false, structuredContent, content: [{ type: "text", text: renderRecentChanges(structuredContent) }] };
889
+ }
890
+
576
891
  // ../providers/index.mjs
577
892
  var PROVIDER_TOOL = {
578
893
  name: "provider_playbook",
@@ -1185,7 +1500,7 @@ function mcpVersion() {
1185
1500
  } catch {
1186
1501
  }
1187
1502
  }
1188
- found ??= true ? "1.7.1" : void 0;
1503
+ found ??= true ? "1.7.2" : void 0;
1189
1504
  if (!found || !PLAIN_VERSION.test(found)) {
1190
1505
  throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
1191
1506
  }
@@ -1409,6 +1724,7 @@ var ALL_TOOLS = [
1409
1724
  ...npmTools,
1410
1725
  ...WORK_TOOLS,
1411
1726
  PROVIDER_TOOL,
1727
+ RECENT_PROVIDER_CHANGES_TOOL,
1412
1728
  ...LIVE_TOOLS
1413
1729
  ];
1414
1730
  function parseJsonObjectFromToolText(text) {
@@ -1434,12 +1750,14 @@ function isCompletedNegativeNpmVerdict(receipt) {
1434
1750
  }
1435
1751
  async function callTool(name, args) {
1436
1752
  if (name === "provider_playbook") return providerPlaybook(args).content[0].text;
1753
+ if (name === "recent_provider_changes") return recentProviderChanges(args).content[0].text;
1437
1754
  return runVibeRaven(buildToolArgs(name, args || {}), args?.cwd);
1438
1755
  }
1439
1756
  async function handleRequest(method, params) {
1440
1757
  if (method === "tools/list") return { tools: ALL_TOOLS };
1441
1758
  if (method === "tools/call") {
1442
1759
  if (params.name === "provider_playbook") return providerPlaybook(params.arguments);
1760
+ if (params.name === "recent_provider_changes") return recentProviderChanges(params.arguments ?? {});
1443
1761
  const args = params.arguments || {};
1444
1762
  const cliArgs = buildToolArgs(params.name, args);
1445
1763
  const run = await runVibeRavenDetailed(cliArgs, args.cwd);
package/package.json CHANGED
@@ -1,70 +1,70 @@
1
- {
2
- "name": "@viberaven/mcp",
3
- "version": "1.7.1",
4
- "description": "MCP server for VibeRaven: lets Claude Code, Cursor and Codex run the Supabase RLS and security check on an AI-built Vercel + Supabase app and read the findings.",
5
- "license": "MIT",
6
- "author": "VibeRaven",
7
- "mcpName": "io.github.ohad6k/viberaven",
8
- "homepage": "https://viberaven.dev/mcp.md",
9
- "repository": {
10
- "type": "git",
11
- "url": "git+https://github.com/ohad6k/VibeRaven.git",
12
- "directory": "packages/mcp"
13
- },
14
- "bugs": {
15
- "url": "https://github.com/ohad6k/VibeRaven/issues"
16
- },
17
- "keywords": [
18
- "viberaven",
19
- "mcp",
20
- "claude-code",
21
- "codex",
22
- "cursor",
23
- "launch-readiness",
24
- "production",
25
- "supabase-rls",
26
- "row-level-security",
27
- "rls",
28
- "supabase-security",
29
- "security-scanner",
30
- "security",
31
- "lovable",
32
- "bolt",
33
- "secrets",
34
- "service-role-key",
35
- "stripe-webhook",
36
- "postgres",
37
- "migrations"
38
- ],
39
- "publishConfig": {
40
- "access": "public",
41
- "tag": "next"
42
- },
43
- "bin": {
44
- "viberaven-mcp": "dist/server.js"
45
- },
46
- "files": [
47
- "dist",
48
- "README.md"
49
- ],
50
- "engines": {
51
- "node": ">=20"
52
- },
53
- "scripts": {
54
- "build": "node scripts/build.mjs",
55
- "typecheck": "tsc -p tsconfig.json --noEmit",
56
- "presmoke": "npm run build",
57
- "smoke": "node scripts/smoke.mjs",
58
- "prepublishOnly": "npm run build && npm test",
59
- "pretest": "npm run build",
60
- "test": "vitest run"
61
- },
62
- "dependencies": {
63
- "@modelcontextprotocol/sdk": "^1.0.0"
64
- },
65
- "devDependencies": {
66
- "esbuild": "^0.25.0",
67
- "typescript": "^5.8.0",
68
- "vitest": "^3.2.0"
69
- }
70
- }
1
+ {
2
+ "name": "@viberaven/mcp",
3
+ "version": "1.7.2",
4
+ "description": "MCP server for VibeRaven: lets Claude Code, Cursor and Codex run the Supabase RLS and security check on an AI-built Vercel + Supabase app and read the findings.",
5
+ "license": "MIT",
6
+ "author": "VibeRaven",
7
+ "mcpName": "io.github.ohad6k/viberaven",
8
+ "homepage": "https://viberaven.dev/mcp.md",
9
+ "repository": {
10
+ "type": "git",
11
+ "url": "git+https://github.com/ohad6k/VibeRaven.git",
12
+ "directory": "packages/mcp"
13
+ },
14
+ "bugs": {
15
+ "url": "https://github.com/ohad6k/VibeRaven/issues"
16
+ },
17
+ "keywords": [
18
+ "viberaven",
19
+ "mcp",
20
+ "claude-code",
21
+ "codex",
22
+ "cursor",
23
+ "launch-readiness",
24
+ "production",
25
+ "supabase-rls",
26
+ "row-level-security",
27
+ "rls",
28
+ "supabase-security",
29
+ "security-scanner",
30
+ "security",
31
+ "lovable",
32
+ "bolt",
33
+ "secrets",
34
+ "service-role-key",
35
+ "stripe-webhook",
36
+ "postgres",
37
+ "migrations"
38
+ ],
39
+ "publishConfig": {
40
+ "access": "public",
41
+ "tag": "next"
42
+ },
43
+ "bin": {
44
+ "viberaven-mcp": "dist/server.js"
45
+ },
46
+ "files": [
47
+ "dist",
48
+ "README.md"
49
+ ],
50
+ "engines": {
51
+ "node": ">=20"
52
+ },
53
+ "scripts": {
54
+ "build": "node scripts/build.mjs",
55
+ "typecheck": "tsc -p tsconfig.json --noEmit",
56
+ "presmoke": "npm run build",
57
+ "smoke": "node scripts/smoke.mjs",
58
+ "prepublishOnly": "npm run build && npm test",
59
+ "pretest": "npm run build",
60
+ "test": "vitest run"
61
+ },
62
+ "dependencies": {
63
+ "@modelcontextprotocol/sdk": "^1.0.0"
64
+ },
65
+ "devDependencies": {
66
+ "esbuild": "^0.25.0",
67
+ "typescript": "^5.8.0",
68
+ "vitest": "^3.2.0"
69
+ }
70
+ }